The section your link pointed to isn't on Hacktron's page any more, so we've brought you to the top.
Hacktron is an AI-powered security code-review platform. Our AI agents review your repositories for exploitable vulnerabilities and surface them as pull-request comments and dashboard findings.
Hacktron is a commercial AI offensive-security platform that runs automated vulnerability analysis against source code and pull requests, offered as a hosted service with an API rather than a local tool. It scans repositories on Bitbucket and Azure DevOps, letting practitioners walk a taint trace interactively from source to sink, triage findings in bulk, and export results into reporting or downstream workflows, with an API surface covering scans, findings, and package-level risk verdicts. It is built for application security and product security teams working inside existing code review pipelines rather than for standalone red-team engagements, and its live AI run capability points to use during active assessments rather than only scheduled scans. The category is AI-driven offensive security tooling, sitting alongside code-scanning and SASTSASTStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment.-adjacent products rather than traditional network penetration testers.
Hacktron is an AI-powered security code-review platform. Our AI agents review your repositories for exploitable vulnerabilities and surface them as pull-request comments and dashboard findings.
Which vulnerabilities in this pull request would block a merge if left unfixed?
scans the changed code and surfaces exploitable findings as pull-request comments, with severity and an OWASP or CWE category attached so a reviewer can decide before merging
Where in my code does this tainted input actually get used unsafely?
traces the data flow interactively from the point it enters the code to the point it reaches a dangerous sink, so a reviewer can see the path rather than just the flagged line
Which of these findings are duplicates or not worth my time?
lets a reviewer triage many findings at once, marking items as duplicate or changing status in bulk instead of working through them one by one
How do I get these findings in front of people who don't use the dashboard?
exports findings, or a scan's threat model and architecture notes, for reporting or downstream workflows
Is this package or dependency carrying a known risk?
exposes package-level risk verdicts through the findings API so a build or review step can check a dependency before it's pulled in
Which fix recommendation should I hand to the engineer who owns this code?
attaches a plain-language fix recommendation and CWE identifier to each finding, where the scan engine can supply one, visible in the finding's detail view
50 capabilities
· 2 backed by code, an API document or a real run
Built from Hacktron's releases, docs, README and our own runs.
“Seen” marks the month we first spotted a release the vendor didn't date.
Group names and tags are our labels.
+Repository scanningverifiedScans repositories and surfaces findings, with support for managing scan state and results.24 releases · 8 other sources · first seen May 2026▸
The Methodology section of a whitebox scan report now shows how many functions each area selected instead of an arbitrary list of five names, and Coverage Detail caps the unselected entry-points table at 50 rows.
Findings get an identity, a history, and a command palette · Oct 2026
· source
· release history
Expands the Repositories table to show Repository and Owner as separate columns alongside Open Findings, PR Scans, and Last Scan, with a platform filter scoped to only connected providers.
Choose GitHub repositories without leaving Hacktron · Sep 2026
· source
· release history
Shows the engine-reported failure reason on the scan detail page when a scan fails.
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
Pins a GitLab Whitebox Scan to a specific tag or commit SHA instead of the tip of a branch.
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
Pin a Whitebox Scan in GitLab to a specific tag or commit SHA rather than the branch tip
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
example
When launching a Whitebox pentest, narrow the scan to only the directories that are in scope — such as a single service directory — instead of scanning the entire repository.$ In the Whitebox pentest wizard, advance to the Scope step, uncheck all top-level folders in the checkbox file tree, then check only the folders you want scanned (e.g.
Scope your pentest to exactly the folders that matter · Oct 2026
· source
Pin a Whitebox Scan in GitLab to a specific commit for reproducible scans.$ In the Whitebox Scan settings for a GitLab repository, enter the target commit SHA instead of relying on the default branch tip.
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
Target a specific release tag for a GitLab Whitebox Scan instead of scanning the current branch tip — useful for auditing a pinned release candidate.$ In the Hacktron web app, go to Whitebox Scans > New Scan, select your GitLab repository, then enter the tag name (e.g. `v2.4.1`) or commit SHA in the 'Tag or commit' field before starting the scan.
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
+Pull request scanningshippedScans Bitbucket pull requests to surface vulnerabilities before code is merged.25 releases · 4 other sources · first seen Apr 2026▸
release
25 total
Adds GET /pr-review-settings and PATCH /pr-review-settings endpoints for managing PR review settings.
1.0 · Nov 2026
· source
· release history
(improved) Code Review limits are raised: pull requests with up to 500 changed files are now accepted, up from 200, and OSS organizations now get 50 free PR reviews per month, up from the previous limit.
Scope your pentest to exactly the folders that matter · Oct 2026
· source
· release history
The trial activation modal now has an enable-all button to turn on PR reviews for every connected repository in one step.
Scope your pentest to exactly the folders that matter · Oct 2026
· source
· release history
Organization admins can now turn off automated code review comments for the whole org from Settings.
Scope your pentest to exactly the folders that matter · Oct 2026
· source
· release history
Adds per-repository PR-review toggle to keep a repository available to Hacktron while independently switching its automatic PR reviews on or off.
Choose GitHub repositories without leaving Hacktron · Sep 2026
· source
· release history
example
Stop Hacktron from posting automated code review comments on every pull request across the whole organization.$ In Hacktron, go to Settings, find the automated code review comments control, and turn it off at the org level.
Scope your pentest to exactly the folders that matter · Oct 2026
· source
Keep a repo visible in Hacktron for findings tracking while disabling automatic PR reviews — useful for low-priority or archived repos.$ In Hacktron, go to Repositories, find the target repository, and toggle 'Automatic PR Reviews' off while leaving the repository enabled in the GitHub integration.
Choose GitHub repositories without leaving Hacktron · Sep 2026
· source
Trigger a re-review of an already-reviewed commit to get the current status without waiting for the next push.$ @hacktronai review
Choose GitHub repositories without leaving Hacktron · Sep 2026
· source
Trigger a white-box review of a specific pull request using the new command syntax.$ @hacktronai review
June 7, 2026 · Jun 2026
· source
+Findings exportverifiedExports findings for use in reporting or downstream workflows.15 releases · 3 other sources · first seen Mar 2026▸
release
15 total
Findings with recorded live-validation evidence gain a Live Validation section in the PDF report showing what the attempt established, what it did not establish, any blocker, and observed output for successful exploits.
See what a Whitebox scan actually established · Oct 2026
· source
· release history
Whitebox PDF reports now include repositories and targets in scope, testing window, severity rubric, limitations, confidentiality notice, and — where available — methodology and code-coverage detail.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
See what a Whitebox scan actually established · Oct 2026
· source
· release history
Expands pentest PDF exports with more per-finding detail, display-order finding numbers, and syntax-highlighted code blocks.
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
Export your findings for reporting or downstream workflows.
Walk a taint trace, export your findings, and scan Bitbucket PRs · seen Aug 2026
· source
· release history
Exports findings as CSV, JSON, or SARIF from the UI filtered by current view
Walk a taint trace, export your findings, and scan Bitbucket PRs · Jul 2026
· source
· release history
Findings export directly from UI as CSV, JSON, or SARIF respecting active filters
July 15, 2026 · Jul 2026
· source
· release history
example
Programmatically export findings for automation pipelines$ curl -H 'Authorization: Bearer <token>' 'https://app.hacktron.ai/rest/findings/export?format=json'
Walk a taint trace, export your findings, and scan Bitbucket PRs · Jul 2026
· source
+Taint trace analysisshippedLets analysts walk taint traces interactively to follow data flows from source to sink during code analysis.11 releases · first seen Apr 2026▸
release
11 total
Connects GitHub Enterprise Server to appliances via a GitHub App installation instead of a personal access token.
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
Connects self-managed GitLab instances to appliances for merge-request scanning, enabling the Reviews link, PR Review dashboard tabs, and source control settings.
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
Walk a taint trace interactively to follow data flows from source to sink during code analysis.
Walk a taint trace, export your findings, and scan Bitbucket PRs · seen Aug 2026
· source
· release history
Interactive taint trace reader allowing step-through of source, propagation, and sink steps in the annotated code view
July 15, 2026 · Jul 2026
· source
· release history
Adds a Finding history section showing a timeline of how each finding changed from one scan to the next.
Findings open straight into the taint trace · Jun 2026
· source
· release history
The full-page finding view now opens directly into the taint trace with smooth collapse animations.
Findings open straight into the taint trace · Jun 2026
· source
· release history
+AI-assisted analysisshippedRuns real-time AI-assisted analysis during assessments.9 releases · first seen Jun 2026▸
release
9 total
Supports live AI runs, enabling real-time AI-assisted analysis during assessments.
Azure DevOps is here, plus bulk triage and live AI runs · seen Aug 2026
· source
· release history
Adds a live automation run transcript showing the AI agent’s reasoning, tool calls, and output in real time on the run detail page.
Azure DevOps is here, plus bulk triage and live AI runs · Aug 2026
· source
· release history
Adds auto-resolution of triage threads when commands (!fp, !valid, !accepted_risk, !fixed) are posted as replies to GitHub PR or GitLab MR comments.
Azure DevOps is here, plus bulk triage and live AI runs · Aug 2026
· source
· release history
Adds live AI run transcript on the run detail page to view agent reasoning and tool calls in real time
August 3, 2026 · Aug 2026
· source
· release history
Adds auto-resolution of triage threads when posting commands (!fp, !valid, !accepted_risk, !fixed) as replies on GitHub PR or GitLab MR comments
August 3, 2026 · Aug 2026
· source
· release history
Adds a Fix with AI button in Slack alerts that deep-links directly into Cursor or Claude to open the issue and start fixing.
June 10, 2026 · Jun 2026
· source
· release history
+Bulk triageshippedAllows practitioners to triage multiple findings at the same time.6 releases · 1 other source · first seen Mar 2026▸
release
Mark a single finding as Closed directly from its status menu, keyboard shortcut, or command palette — the same place used to set False Positive.
Scope your pentest to exactly the folders that matter · Oct 2026
· source
· release history
Introduces bulk triage, allowing practitioners to triage multiple findings simultaneously.
Azure DevOps is here, plus bulk triage and live AI runs · seen Aug 2026
· source
· release history
Adds bulk findings triage allowing status or severity changes for multiple selected findings across all filtered pages in one action.
Azure DevOps is here, plus bulk triage and live AI runs · Aug 2026
· source
· release history
PR and MR checks update on triage: GitHub check or GitLab commit status flips to passing immediately when a finding is marked as false positive or accepted risk, and reverts to failing if the finding is reopened.
June 18, 2026 · Jun 2026
· source
· release history
Enables full Markdown rendering in findings descriptions, dismiss reasons, and comments plus one-click report copy
April 6, 2026 · Apr 2026
· source
· release history
Enables triage of findings directly in the browser app with dismiss options and an activity thread
Triage findings without leaving the browser · Mar 2026
· source
· release history
example
Filter the findings list to a specific set of findings by pasting their IDs — useful when a ticket references multiple findings you want to triage together.$ In the findings search box, paste: HT-1042 HT-1078 HT-1091
Findings get an identity, a history, and a command palette · Oct 2026
· source
+Azure DevOps integrationshippedConnects findings and workflows directly with Azure DevOps projects.6 releases · first seen May 2026▸
Also counts toward: Ticketing integration
release
Supports Azure DevOps repositories for remediation automations — fix pull requests can now be opened and tracked on Azure DevOps alongside GitHub and GitLab.
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
Adds Microsoft account connection in Personal settings to link Azure DevOps identities
August 19, 2026 · Aug 2026
· source
· release history
Adds Azure DevOps integration to automatically review pull requests using a personal access token
August 3, 2026 · Aug 2026
· source
· release history
Adds Azure DevOps PR scanning as a new integration platform, connecting via personal access token to automatically review pull requests.
Azure DevOps is here, plus bulk triage and live AI runs · Aug 2026
· source
· release history
Adds Azure DevOps integration, enabling teams to connect Hacktron findings and workflows directly with Azure DevOps projects.
Azure DevOps is here, plus bulk triage and live AI runs · seen Aug 2026
· source
· release history
Enhances Linear integration with default project selection, finding severity-to-priority mapping, and status mirroring.
May 19, 2026 · May 2026
· source
· release history
+Multi-factor authenticationshippedEnables administrators to enforce MFA requirements across their organization for account security.6 releases · first seen Jun 2026▸
Also counts toward: Multi-factor authentication
release
Consolidates Account and Settings into a single Personal settings page with sections for Profile, Security, Connected accounts, Preferences, Sessions, and Organizations.
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
Allows any organization member to create, rotate, and revoke their own API keys from personal settings without owner or admin involvement.
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
Appliance operators can allow specific private Git hosts, add trusted CA certificates, and collect masked support bundles without an outbound internet connection (air-gapped support).
Separate credit accounts and more on-premises scan options · Aug 2026
· source
· release history
Adds a dedicated SSO sign-in page and Single sign-on (SSO) button on the login screen for SAML/OIDC authentication with IdP round-trip token support
A new Context page for your repositories, applications, and threat models · Jun 2026
· source
· release history
Admins can now enforce multi-factor authentication (MFA) requirements across their organization for account security
Control your scans and account security like never before · Jun 2026
· source
· release history
Admins can enforce Multi-factor authentication (MFA) across their organization via new account security controls
June 15, 2026 · Jun 2026
· source
· release history
+Login automation previewshippedLets users validate login credentials and instructions against a deployed target in a preview session before launching a dynamic validation scan.3 releases · 1 other source · first seen Sep 2026▸
release
Adds new pentests endpoints: DELETE /pentests/{id}, PATCH /pentests/{id}, POST /pentests, POST /pentests/{id}/estimate, POST /pentests/{id}/login-checks, and POST /pentests/{id}/start.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
1.0 · Nov 2026
· source
· release history
Inline browser-auth audit instructions in the whitebox scan wizard's target step now appear directly on the page with live verification status, replacing the separate modal.
Findings get an identity, a history, and a command palette · Oct 2026
· source
· release history
Adds login instruction preview for dynamic validation in the Whitebox scan wizard: supply login instructions and test credentials, then preview the browser session before starting so Hacktron can authenticate against deployed targets during finding validation.
Check your fixes without repeating the full assessment · Sep 2026
· source
· release history
example
Validate that login automation will work against your deployed target before committing a dynamic-validation scan.$ In the Whitebox scan wizard, navigate to the dynamic validation step, enter your login instructions and test credentials, then click the preview button to open the browser session and confirm…
Check your fixes without repeating the full assessment · Sep 2026
· source
+Whitebox Scan archive supportshippedEnables on-premises appliances to upload compressed source archives (.zip, .7z, .tar.gz, .tgz) for whitebox scanning.4 releases · first seen Jun 2026▸
Adds *.zip, *.7z, *.tar.gz, and *.tgz upload options for Whitebox Scans in on-premises deployments
August 19, 2026 · Aug 2026
· source
· release history
On-premises deployments can now upload .zip, .7z, .tar.gz, and .tgz source archives for Whitebox Scans
Separate credit accounts and more on-premises scan options · Aug 2026
· source
· release history
Whitebox scans from uploaded archives take the archive's filename as the scan name
Dismiss a finding and your PR check clears instantly · Jun 2026
· source
· release history
+Context navigationshippedProvides a dedicated Context page to view and navigate all repositories and applications sorted by recent updates.3 releases · 1 other source · first seen Apr 2026▸
release
The Repositories page shows a notice when PR Review is toggled on for a repo but no active trial or subscription backs it, with a direct link to start a trial.
Findings get an identity, a history, and a command palette · Oct 2026
· source
· release history
Adds a dedicated Context page with Repositories and Applications tabs to browse code knowledge sorted by threat-model update time
A new Context page for your repositories, applications, and threat models · Jun 2026
· source
· release history
Adds context documents upload feature for repository notes to inform review conventions
April 6, 2026 · Apr 2026
· source
· release history
example
Navigate to the new Context page to view all repositories and applications sorted by recent threat model updates.$ In the Hacktron console, click 'Context' in the left sidebar.
A new Context page for your repositories, applications, and threat models · Jun 2026
· source
+Finding retest workflowshippedAllows organizations to request targeted retesting of specific findings after remediation, tracking outcomes and notes in a dedicated history.2 releases · 2 other sources · first seen Sep 2026▸
release
Adds a whitebox retest wizard to request a retest for a completed scan directly from the scans list or scan detail page, covering all reported findings except false positives and accepted risk, and shows retest status and results on the scan detail page once a retest is complete.
Findings get an identity, a history, and a command palette · Oct 2026
· source
· release history
Adds Retest findings workflow on completed hosted Whitebox scans: select findings, provide fix instructions, and the Hacktron pentest team records each outcome and notes; completed retests appear in the scan's retest history and PDF report.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Check your fixes without repeating the full assessment · Sep 2026
· source
· release history
example
Request a whitebox retest after a scan is complete to verify that reported findings (excluding false positives and accepted risk) have been remediated.$ Navigate to Scans > [completed scan] > Retest, then follow the retest wizard to submit the request. Track status and results on the scan detail page.
Findings get an identity, a history, and a command palette · Oct 2026
· source
After remediating findings from a Whitebox scan, request targeted retests instead of re-running the full assessment.$ In a completed Whitebox scan, go to Retest findings, select the findings you have fixed, enter your fix instructions, and submit.
Check your fixes without repeating the full assessment · Sep 2026
· source
+OWASP category filteringshippedAdds OWASP Top 10:2025 category badges and filters to the findings list.4 releases · first seen Aug 2026▸
release
Adds Source, Reopened, and Date range filters to the findings list, each saved in the URL, and a CWE name tooltip on the CWE badge so the full weakness name is visible without leaving the page.
Findings get an identity, a history, and a command palette · Oct 2026
· source
· release history
Filter the findings list by the OWASP Top 10:2025 category (appears in table/drawer)
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
Adds OWASP category badges and a corresponding filter for the findings list.
Azure DevOps is here, plus bulk triage and live AI runs · Aug 2026
· source
· release history
Adds OWASP category badge and filter to the findings list
August 3, 2026 · Aug 2026
· source
· release history
+Application groupingshippedGroups multiple repositories into an Application to enable merged threat modeling and consolidated scanning.3 releases · 1 other source · first seen Jun 2026▸
release
Adds the OWASP Top 10:2025 category field on findings with table/drawer display and list filtering
September 18, 2026 · Sep 2026
· source
· release history
Adds the ability to group repositories into an Application for merged threat modeling and scanning
June 23, 2026 · Jun 2026
· source
· release history
Gains ability to group repositories into an Application so Hacktron merges member threat models for application-level scanning and upload fold-in
A new Context page for your repositories, applications, and threat models · Jun 2026
· source
· release history
example
Filter findings by OWASP Top 10:2025 category using backtick-delimited category name to avoid quote issues.$ In the findings view, use the filter dropdown to select 'OWASP Top 10:2025' and type a category like `Injection`
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
+Finding history timelineshippedDisplays a timeline in the findings view showing how each finding changed from one scan to the next.2 releases · 2 other sources · first seen Jun 2026▸
release
Adds a finding timeline showing how each finding changed from one scan to the next
June 1, 2026 · Jun 2026
· source
· release history
Adds a Finding history section showing a timeline of how each finding changed from one scan to the next.
Findings open straight into the taint trace · Jun 2026
· source
· release history
example
Configure your organization to set a default severity threshold for PR checks, allowing individual repos to override it.$ In Settings > Organization > PR/MR Checks, set 'Fail-on severity' (e.g., 'high')
A new Context page for your repositories, applications, and threat models · Jun 2026
· source
View the evolution of a specific finding across multiple scans via its new timeline.$ In the console, go to a finding's full-page view to see the 'Finding history' timeline.
Findings open straight into the taint trace · Jun 2026
· source
+Scan progress and cost trackingshippedDisplays live scan execution progress and real-time billing updates, plus estimates costs before execution.4 releases · first seen Mar 2026▸
release
Adds real-time whitebox billing streaming so users can watch findings arrive as the scan runs
Watch findings arrive as a scan runs · Mar 2026
· source
· release history
Adds live scan progress streaming so you can watch findings arrive as a scan runs
March 18, 2026 · Mar 2026
· source
· release history
Enables cost estimation before starting a scan or pentest
March 18, 2026 · Mar 2026
· source
· release history
Adds pre-scan cost estimation for scans and pentests before execution begins
Watch findings arrive as a scan runs · Mar 2026
· source
· release history
+Usage monitoring dashboardshippedDisplays consumption and overage data for the billing period across different tool surfaces.3 releases · first seen Jun 2026▸
Reorganizes usage page into three tabs: PR Reviews, Automations, and Whitebox
August 3, 2026 · Aug 2026
· source
· release history
New owner-only Usage page shows usage and overage for the billing period
Share Code Review limits across your whole org · Jun 2026
· source
· release history
+Security enforcement controlsshippedProvides admin-level controls to enforce security policies such as MFA across the organization.3 releases · first seen Jun 2026▸
Also counts toward: Multi-factor authentication
release
Tooltips and prompts at every auto-assignment opt-in point now disclose that bot PR authors take billable seats, and the excluded-authors filter note clarifies that excluded authors never consume a seat.
Scope your pentest to exactly the folders that matter · Oct 2026
· source
· release history
Admins can now enforce multi-factor authentication (MFA) requirements across their organization for account security
Control your scans and account security like never before · Jun 2026
· source
· release history
Admins can enforce Multi-factor authentication (MFA) across their organization via new account security controls
June 15, 2026 · Jun 2026
· source
· release history
+Findings list filteringshippedAdds Source, Reopened, and Date range filters to the findings list, each persisted in the URL for shareability.2 releases · first seen Oct 2026▸
Adds Source, Reopened, and Date range filters to the findings list, each saved in the URL, and a CWE name tooltip on the CWE badge so the full weakness name is visible without leaving the page.
Findings get an identity, a history, and a command palette · Oct 2026
· source
· release history
+Whitebox pentest scope configurationshippedLets users define the scope of a Whitebox pentest by selecting specific folders to include or exclude via a checkbox file tree in the pentest wizard.2 releases · first seen Oct 2026▸
release
Adds new pentests endpoints: DELETE /pentests/{id}, PATCH /pentests/{id}, POST /pentests, POST /pentests/{id}/estimate, POST /pentests/{id}/login-checks, and POST /pentests/{id}/start.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
1.0 · Nov 2026
· source
· release history
Scope a Whitebox pentest to specific folders by picking paths to include or exclude in a checkbox file tree inside the new Scope step of the Whitebox pentest wizard.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Scope your pentest to exactly the folders that matter · Oct 2026
· source
· release history
+Compliance attestation lettersshippedProvides a page where Hacktron-issued attestation letters are listed with unique shareable links and PDF downloads accessible to auditors without a Hacktron account.1 release · 1 other source · first seen Oct 2026▸
release
Access an Attestation Letters page where Hacktron-issued letters appear with a unique shareable link and a PDF download that auditors can view without logging in.
Scope your pentest to exactly the folders that matter · Oct 2026
· source
· release history
example
Share a compliance attestation letter with a customer or auditor who does not have a Hacktron account.$ Go to your organization's Attestation Letters page, copy the unique shareable link next to the relevant letter, and send it to the recipient — they can view or download the PDF without logging in.
Scope your pentest to exactly the folders that matter · Oct 2026
· source
+High-cost approval workflowshippedPrompts users to contact the support team when whitebox scan estimates exceed 5,000 credits during the approval flow.2 releases · first seen Sep 2026▸
release
The final Whitebox review step is rebuilt as a structured summary panel with Source, Target, Access, and Context sections, each with an Edit button and visible verification status.
Scope your pentest to exactly the folders that matter · Oct 2026
· source
· release history
Adds a contact-the-team prompt for organizations using the large-estimate approval flow when Whitebox estimates exceed 5,000 credits.
Choose GitHub repositories without leaving Hacktron · Sep 2026
· source
· release history
+Organization member search and filteringshippedProvides advanced search, filtering, and pagination across the full member list to find users by name, email, SCM username, role, or seat type.2 releases · first seen Sep 2026▸
release
The People page now splits into a Members tab and an Invitations tab, with revoked invitations listed with a Delete option instead of disappearing.
Scope your pentest to exactly the folders that matter · Oct 2026
· source
· release history
Adds name, email, and SCM username search to the People list, with filters by role or Code Review seat, plus sort and pagination across the full member list rather than only loaded rows.
Check your fixes without repeating the full assessment · Sep 2026
· source
· release history
+Unified integration managementshippedProvides a centralized page to view connection status, manage provider access, and handle repository selection across all connected external services.2 releases · first seen Oct 2026▸
release
Connecting a GitLab installation no longer requires completing every step before saving — partial setups can be saved, and the connection page shows only the actions available at your current access level.
Scope your pentest to exactly the folders that matter · Oct 2026
· source
· release history
Adds a unified Integrations page that lists all providers with connection details, repository counts where applicable, a Connect or Manage action, status badges for connected providers, and inline actions for connections needing attention.
See what a Whitebox scan actually established · Oct 2026
· source
· release history
+Appliance air-gap supportshippedAllows appliance operators to configure trusted CAs and private Git hosts while collecting masked support bundles in environments without outbound internet access.2 releases · first seen Aug 2026▸
Also counts toward: Air-gapped deployment, On-premises appliance
release
On-prem appliances that cannot reach GitHub.com now disable the GitHub.com integration card with a specific reason (DNS, blocked, or TLS) instead of failing at the code exchange.
Findings get an identity, a history, and a command palette · Oct 2026
· source
· release history
Appliance operators can allow specific private Git hosts, add trusted CA certificates, and collect masked support bundles without an outbound internet connection (air-gapped support).
Separate credit accounts and more on-premises scan options · Aug 2026
· source
· release history
+Workflow status syncshippedSyncs triage status in the web app, Slack, PR comments, or API to Linear workflow states.2 releases · first seen Sep 2026▸
Also counts toward: Ticketing integration
release
Adds two-way Jira and Linear status sync: finding status changes propagate to linked issues and supported issue status changes flow back into Hacktron, with each direction independently toggled by organization admins in integration settings; Jira updates follow the project workflow's available transitions.
See what a Whitebox scan actually established · Oct 2026
· source
· release history
Sync triage status to Linear workflow states when triaging from the web app, Slack, PR comment, or API
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
+Appliance license management and billingshippedDisplays licensee details, expiry dates, seat counts, and scan blocking warnings on appliance settings, with separate billing for Automation and Whitebox Scan credits.2 releases · first seen Aug 2026▸
release
Adds license detail and expiry warnings to organization settings on appliances — showing licensee, expiry date, days remaining, seat count, and covered products — with a 30-day-out banner and scan blocking after the grace deadline.
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
Billing now shows separate accounts for Automation credits and Whitebox Scan Credits, each with its own balance, current-period usage, purchase flow, and history; auto top-up is available for Automation credits only.
Separate credit accounts and more on-premises scan options · Aug 2026
· source
· release history
+Appliance scan quota enforcementshippedCaps the total number of full scans an appliance license permits, enforced at the start of each scan attempt including restarts.1 release · 1 other source · first seen Sep 2026▸
release
Adds max_scans entitlement field to appliance licenses, capping the total number of full scans that may start over the life of the license, checked at scan start including restarts.
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
example
Cap the total scans an appliance license permits so a max_scans quota is enforced from the first scan attempt.$ max_scans: 500
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
+Personal API key generationshippedAllows users to generate personal API keys for automation without administrative approval.1 release · 1 other source · first seen Sep 2026▸
release
Create, rotate, and revoke personal API keys from Personal settings without admin intervention
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
example
Generate personal API keys for automation without requiring admin assistance.$ Navigate to Personal settings > Connected accounts and use the new management controls to create or rotate an API key.
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
+Automated triage thread resolutionshippedAuto-resolves triage threads when specific commands are posted as replies to pull request or merge request comments.2 releases · first seen Aug 2026▸
release
Adds auto-resolution of triage threads when commands (!fp, !valid, !accepted_risk, !fixed) are posted as replies to GitHub PR or GitLab MR comments.
Azure DevOps is here, plus bulk triage and live AI runs · Aug 2026
· source
· release history
Adds auto-resolution of triage threads when posting commands (!fp, !valid, !accepted_risk, !fixed) as replies on GitHub PR or GitLab MR comments
August 3, 2026 · Aug 2026
· source
· release history
+Finding duplicate detectionshippedAllows programmatically marking findings as duplicates via a dedicated field in the update tool.2 releases · first seen Jun 2026▸
release
Updates the update_finding MCP tool to accept a duplicate_of field for programmatically marking findings as duplicates
A new Context page for your repositories, applications, and threat models · Jun 2026
· source
· release history
Adds the duplicate_of field to the update_finding MCP tool
June 23, 2026 · Jun 2026
· source
· release history
+Jira ticket filingshippedFiles tickets directly from findings with large project search and assignee lookup.2 releases · first seen Jun 2026▸
Also counts toward: Ticketing integration
release
Enables richer Jira ticketing with large project search, assignee lookup, and finding links
June 7, 2026 · Jun 2026
· source
· release history
Enables search within large Jira projects and assignee lists when filing tickets from findings
Scan self-hosted GitHub Enterprise Server · Jun 2026
· source
· release history
+Configurable trial periodsshippedAllows organizations to select custom trial lengths and receive prompts when usage limits are reached.2 releases · first seen May 2026▸
release
Trials can run for a length you choose, with a clear prompt when you reach their limits
May 13, 2026 · May 2026
· source
· release history
Adds Custom trial duration allowing selectable trial lengths with usage limit prompts.
50 PR reviews a seat, then $1 each instead of a wall · May 2026
· source
· release history
+Organization resubscriptionshippedProvides a one-click resubscribe button for canceled organizations to restore previous plans.2 releases · first seen May 2026▸
release
Adds Resubscribe button for canceled organizations to restore previous plans in one click.
50 PR reviews a seat, then $1 each instead of a wall · May 2026
· source
· release history
Canceled organizations get a Resubscribe button to pick their old plan back up
May 13, 2026 · May 2026
· source
· release history
+Linear issue creationshippedGenerates Linear issues directly from findings with pre-filled details.2 releases · first seen Apr 2026▸
release
Allows creating a Linear issue directly from a finding with details pre-filled
Drive Hacktron from your own scripts · Apr 2026
· source
· release history
Adds ability to create Linear issues directly from findings with pre-filled details
April 20, 2026 · Apr 2026
· source
· release history
+External scan sharingshippedAllows sharing scan results via read-only public pages for external stakeholders.1 release · 1 other source · first seen Mar 2026▸
release
Adds support for sharing a scan and its findings through public, read-only pages
March 1, 2026 · Mar 2026
· source
· release history
example
Share scan results externally with stakeholders who need read-only access.$ Share a scan and its findings through public, read-only pages.
March 1, 2026 · Mar 2026
· source
+Finding activity and ID trackingshippedAssigns each finding a human-readable stable ID shown throughout the UI with click-to-copy, and provides an Activity tab in the finding detail panel showing the full detection and edit history with actor and changed fields per entry.1 release · first seen Oct 2026▸
release
Adds human-readable, stable finding IDs (shown in the row, panel, full page, and URL, with click-to-copy), an Activity tab in the finding detail panel showing the full detection and edit history with actor and changed fields per entry (switch to a Comments view to see only the thread), finding-scoped actions in…
Findings get an identity, a history, and a command palette · Oct 2026
· source
· release history
+Finding remediation guidanceshippedProvides CWE identifiers and plain-language fix recommendations to findings when supplied by the scan engine.1 release · first seen Sep 2026▸
release
Adds CWE identifier and plain-language fix recommendation to findings in the detail view, where the scan engine supplies them.
A rebuilt findings view, and fix PRs that close themselves · Sep 2026
· source
· release history
+Advanced repository filteringshippedSupports glob patterns for filtering repositories and organization authors.1 release · first seen Aug 2026▸
release
Repository and organization author filters now accept glob patterns (*, **, ?, {a,b})
Separate credit accounts and more on-premises scan options · Aug 2026
· source
· release history
+Automation credit managementshippedEnforces per-run credit caps for automation environments and supports scan restarts.1 release · first seen Aug 2026▸
release
Adds per-run credit caps to automation environments with restart capability
August 3, 2026 · Aug 2026
· source
· release history
+Manual remediation executionshippedSupports running manual remediation scans and displays them in the main runs list.1 release · first seen Aug 2026▸
release
Adds manual remediation runs to the main runs list alongside scheduled automation runs
August 3, 2026 · Aug 2026
· source
· release history
+Slack finding resolutionshippedProvides overflow menu actions in Slack to manually mark findings as resolved.1 release · first seen Jul 2026▸
release
Mark Resolved action added to finding Work Object overflow menu in Slack
July 15, 2026 · Jul 2026
· source
· release history
+Whitebox model tier selectionshippedAllows selecting Default or Legacy AI model tiers when starting a whitebox scan.1 release · first seen Jul 2026▸
release
Model tier selection (Default vs Legacy) when starting a whitebox scan
July 15, 2026 · Jul 2026
· source
· release history
+Enterprise SSO authenticationshippedProvides SAML and OIDC single sign-on login pages for enterprise account access.1 release · first seen Jun 2026▸
Also counts toward: Single sign-on, OIDC SSO, SAML SSO
release
Adds Enterprise SSO sign-in with a dedicated SAML or OIDC login page and button
June 23, 2026 · Jun 2026
· source
· release history
+Inline threat model editingshippedEnables inline reading and editing of threat models with file tree navigation and outline support.1 release · first seen Jun 2026▸
release
Adds inline reading view with file tree and outline for editing threat models while preserving changes across regenerations
June 23, 2026 · Jun 2026
· source
· release history
+GitLab onboarding integrationshippedSupports connecting GitLab repositories directly during account creation and trial setup.1 release · first seen Jun 2026▸
release
Enables direct GitLab connection during the account signup or trial onboarding flow.
June 11, 2026 · Jun 2026
· source
· release history
+Slack-to-IDE deep linkingshippedJumps directly from Slack vulnerability notifications into developer IDEs for resolution.1 other source · first seen Jun 2026▸
example
Use this to quickly jump from a Slack notification directly into an IDE to resolve the issue.$ In Slack, click `Fix with AI` on any Hacktron alert.
Go from a Slack alert to a fix in one click · Jun 2026
· source
+Pull request auto-fixshippedGenerates code fixes directly from vulnerability alerts in pull request comments.1 other source · first seen Jun 2026▸
example
When you spot a vulnerability in a GitHub PR comment, click the prompt to auto-fix the code.$ Steps: In the GitHub PR discussion, locate the Hacktron comment with the severity badge and click 'Fix with AI'.
PR comments that fix the bug for you · Jun 2026
· source
+Slack team invitationsshippedEnables inviting teammates to the organization directly from Slack.1 release · first seen May 2026▸
release
Invite teammates to your Hacktron organization straight from Slack
May 13, 2026 · May 2026
· source
· release history
+Pentest credit purchasingshippedAllows organizations to purchase and allocate credits for pentest services.1 release · first seen Mar 2026▸
release
Adds the ability to buy pentest credits and spend them on pentests
March 1, 2026 · Mar 2026
· source
· release history
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Command line
1 command for Hacktron, each
with where it came from. This tool has no source analysis yet, so there
is no option reference and no captured run beside them.
View
Source
No command matches.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Five scores for Hacktron, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Hacktron puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Where Hacktron turns up in what others publish: how-tos, attack reports that
name it, and incident write-ups. A row says why it is here and quotes where the
article names it; the link goes to the publisher.
The researchers, from a small company called Hacktron , found that by chaining together two unknown vulnerabilities, one in a third-party company called Discourse and one in how OpenAI validates its employees, they…
2 more quotes
Hacktron conducted the entire operation within 72 hours in late July, soon after some of OpenAI’s agents broke containment and hacked the AI platform Hugging Face.
An OpenAI spokesperson confirmed Hacktron’s report and said the vulnerabilities have since been patched.
The three researchers from Hacktron AI, a small security company, were paid $6,500 by OpenAI as part of a bug bounty program, a common practice where tech companies pay ethical hackers to test their security.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can
follow every release here.