HackenProof Docs
  • Welcome
    • HackenProof
      • Services we provide
      • Our resources
    • Integrations
      • Slack
      • Discord
      • Telegram
      • Zapier (Webhook)
        • Zapier -> Lark
        • Zapier -> Linear
        • Zapier -> Jira Service Management
        • Zapier -> PagerDuty
        • Zapier -> Google Chat
        • Zapier -> ClickUp
      • Jira Software
      • GitHub Issue
      • GitLab Issue
      • VDP iFrame
    • FAQ
      • Audit & Bug Bounty (BB)
      • Crowdsourced Audit & BB
      • Penetration testing & BB
    • Emergency
      • Reset 2FA
    • Code of Conduct
    • Referral Program
  • Bug Bounty
    • Bug Bounty process
    • How to start Bug Bounty
    • How to create a VDP
    • Vulnerability classification
      • Web & Mobile
        • Out-of-Scope Bugs
      • Smart contracts
      • Blockchain protocols
    • Reports Basics
      • Points Guide
      • Crafting a well-readable report
  • Dashboard
    • Company dashboard
      • Manage programs
      • Manage reports
      • Share report
      • Labels
      • E2E report encryption
      • Reports decrypting with Mailvelope
      • Users and roles
      • Program/Report Assignee
      • Replenish your balance
      • Integrations
    • Hacker dashboard
      • 👉How to start
      • Submit a report
      • Reports Basics
      • Vulnerability classification
      • 👮‍♂️KYC
      • Сreate a crypto wallet
      • 💸Withdraw bounty
      • Hacker Leaderboard
      • Reset 2FA
      • 🍕HackenProof community
      • Report ID
      • Private Program
      • Contact support
    • Company-Auditor dashboard
      • How to start
      • Add members
      • Submit report
      • Contact support
  • Crowdsourced audit
    • Audit process
    • How to start Audit
    • Supported tech
    • Vulnerability classification
    • Reports Basics
    • Qualified Auditors
    • Judging / Triaging
      • Targets
      • Team
    • Fee & Payments
  • DualDefense Audit
    • What is DualDefence Audit
    • How DualDefence Audit goes
    • DualDefence Audit — researchers' perspective
  • good to know
    • Changelog
    • Branding
    • Vulnerability Disclosure
  • Education
    • Courses
    • Tools
    • Useful sources
Powered by GitBook
On this page
  • How the connection HackenProof -> GitHub issue works
  • How to create a GitHub issue
  • How to connect the GitHub repository to the HackenProof program
  1. Welcome
  2. Integrations

GitHub Issue

Automatically create GitHub issue from HackenProof for reports with any status

PreviousJira SoftwareNextGitLab Issue

Last updated 1 year ago

How the connection HackenProof -> GitHub issue works

This guide explains how GitHub connection helps companies when they run a bounty program at HackenProof.

Once you connect your bug bounty program to your GitHub repository (public or private), you can automatically create a GitHub issue:

remember, you can create a GitHub issue for reports with any STATUS

How to create a GitHub issue

  • Open the report you want to create a GitHub issue from

  • Navigate to the prerequisites section of the report and find the GitHub issue section

  • Press the Create GitHub issue button. As a result, the appropriate issue will be created in your GitHub repository

  • Also, in the report's GitHub section, you will find the link to the newly created issue:

How to connect the GitHub repository to the HackenProof program

  • Open your HackenProof program which you want to connect to HackenProof

  • Navigate to the Integrations tab and open GitHub app

  • Connect your HackenProof program to GitHub by specifying Repository URL and your GitHub API token

Repository URL. Be sure you use the correct Repository URL. Here is a correct sample: https://api.github.com/repos/hackenproof/web3-bug-bounty-platform/issues, where:

  • https://api.github.com/repos/

  • hackenproof/ - company (owner)

  • web3-bug-bounty-platform/issues - repo issue

GitHub API token. To create your token: GitHub Settings -> Developer settings -> Personal access tokens

  • Press the Generate personal access token

  • To create a GitHub issue you will need a token with access to REPO

Make sure to copy your personal access token now. You won’t be able to see it again!

Once you specified Repository URL and your GitHub API token you can connect your bug bounty program with GitHub and start creating GitHub issues

GitHub Settings
Personal settings
Developer settings
Personal access tokens
Generate personal access token