---
title: Changelog
description: Features, improvements, and fixes.
url: https://www.hacktron.ai/docs/changelog
---

# Changelog

## November 12, 2026

### Whitebox

- Completed pentests with no confirmed findings now offer Full and Executive [report](/docs/whitebox/findings-and-reports) downloads, covering scope, methodology, zero counts, and a clear no-findings statement.
- Pentest auth instructions now accept pasted session cookies, so the login agent can sign in to your target without a password.

### Review

- Hacktron now automatically detects when a pull request fixes a finding, labelling it **Fix automatically detected in** in the finding's activity, which also records fix PRs merged after triage.
- When a merged fix PR resolves a finding, Hacktron now confirms the fix on the finding's pull request and Slack threads and closes its open agent fix PRs.
- GitLab merge request and Bitbucket pull request scans now show their author as the creator in Slack finding messages and the scan list, instead of whoever connected the integration.

### Platform

- The [dashboard](/docs/platform/dashboard)'s PR review and Whitebox scan tabs now show an **SLA compliance** ring per severity, with MTTR and a **Past SLA** count linking to overdue findings.

  ![Resolution health, with the MTTR and the share of findings resolved within the SLA for each severity](https://www.hacktron.ai/shots/platform/dashboard/dashboard_resolution_health/light.535be4f7.webp)

- GitLab, Azure DevOps, and GitHub Enterprise Server connection forms now show collapsible **Setup instructions** and keep any connection error until you edit a field or retry.
- The [Bitbucket](/docs/platform/repositories/bitbucket) integration now flags a revoked connection and offers to reconnect it from the integration sheet.
- [Hacktron in Slack](/docs/platform/slack-assistant) now swaps its eyes reaction for a check mark when it finishes a thread, and switches back to eyes for follow-ups.

## November 8, 2026

### Platform

- [Hacktron in Slack](/docs/platform/slack-assistant) now runs scripts in its own sandbox per thread, with web search, access to code hosts and package registries, and one-time approval for other hosts.
- Hacktron in Slack now checks whether a CVE or advisory affects your repositories from their manifests and lock files, including transitive dependencies, and threads get three times the usage budget.
- Hacktron in Slack can now set up pentests of public GitHub repositories from their URL, without you connecting them first.
- Hacktron in Slack now reacts with eyes to each message it will reply to, and tells Slack Connect guests how to use Hacktron from their own workspace.

## November 5, 2026

### Review

- Finding IDs such as `ACME-FD-12` that you mention in a pull request description or comment now become links to the finding on GitHub, GitLab, Bitbucket, and Azure DevOps.
- New [**Update check statuses in source control**](/docs/platform/organization-settings) setting lets you turn off Hacktron check statuses on GitHub, GitLab, Bitbucket, and Azure DevOps separately from review comments.

  ![Source control, with Update check statuses in source control, Post comments to source control and Post system comments turned on](https://www.hacktron.ai/shots/platform/organization-settings/code_review_comments/light.9c385057.webp)

### Platform

- New [Hacktron in Slack](/docs/platform/slack-assistant) agent answers questions about findings, scans, your code, threat models, and the docs, and sets up pentests of repositories, code archives, and signed-in sites.
- Hacktron in Slack can now review pull requests, generate fix pull requests, and, once you approve, change PR review settings, threat models, and applications, posting progress and results.
- New **On a schedule** automation trigger starts [whitebox scans](/docs/platform/automations/scheduled-whitebox-scans) daily, weekly, or monthly, reusing saved scope, login instructions, and a credit limit set up in the Whitebox scan wizard.

  ![A weekly schedule at 02\:00 UTC on the Settings tab, with its next three runs and the whitebox scan action](https://www.hacktron.ai/shots/platform/automations/automation_schedule/light.77f081e6.webp)

- Findings with an open fix PR now show a **Fix in review** badge, and their activity lists pull requests, commits, and Slack messages that mention the finding's ID.

  ![A finding's full page with the Fix in review badge in its header, linking to the open fix pull request](https://www.hacktron.ai/shots/changelog/2026-11-05/finding_fix_in_review/light.a2b7fc8a.webp)

- [Threat models](/docs/platform/context/threat-models) now refresh daily at 03:00 UTC when the default branch changes, application models rebuild with their repositories, and one false-positive or accepted-risk decision triggers an update.
- Log in, sign-up, and SSO pages are redesigned, with the email form first and Google, GitHub, and SSO below it, and password reset now has its own page.

  ::::tabs

  :::tab[Before]

  ![The previous Log in page](https://www.hacktron.ai/shots/changelog/2026-11-05/login_page_before/light.8f94d57c.webp)

  :::

  :::tab[After]

  ![The redesigned Log in page, with the email form first and Google, GitHub, and SSO options below it](https://www.hacktron.ai/shots/changelog/2026-11-05/login_page_after/light.d121bae7.webp)

  :::

  ::::

### API

- You can now [run a pentest through the API](/docs/api/pentests/create-pentest) from draft to start, with `POST /pentests`, `PATCH /pentests/{id}`, `POST /pentests/{id}/login-checks`, `POST /pentests/{id}/estimate`, and `POST /pentests/{id}/start`.
- New `GET /pull-requests`, `GET /pull-requests/details`, and `POST /pull-requests/review` endpoints list open pull requests and start a Hacktron review without anyone commenting on them.
- New `GET /pr-review-settings`, `PATCH /pr-review-settings`, and `POST /repos/pr-reviews` endpoints let you [read and change PR review settings](/docs/api/repos/get-pr-review-settings), including `scm_check_statuses_enabled`, and turn reviews on or off per repository.
- New `POST /scans/{id}/stop` [stops a scan](/docs/api/scans/stop-scan), `POST /archives/uploads` uploads a code archive, `DELETE /pentests/{id}` discards a draft, `GET /credits` returns your credit balance, and `GET /findings/counts` returns finding counts.
- New `POST /findings/{id}/remediate`, `GET /findings/{id}/remediation`, and `GET /credits/automation` endpoints start a fix pull request for a finding, check its progress, and read automation credits.
- New endpoints read and edit context documents, sync threat models, fetch pentest reports with `GET /scans/{id}/report`, open code checkouts with `POST /code-workspaces`, and manage applications with `POST /applications`.

### MCP

- New [MCP tools](/docs/mcp) `create_pentest_draft`, `update_pentest_draft`, `estimate_pentest`, `start_pentest`, `stop_scan`, `discard_pentest_draft`, and `request_archive_upload` let you draft, price, start, stop, and discard pentests, including of code archives.
- New [`verify_pentest_login`](/docs/mcp) tool checks that Hacktron can sign in to each site on a pentest draft, and drafts now accept login targets for signed-in testing.
- The [MCP server](/docs/mcp) now has `list_repositories`, `get_cost_estimation`, `get_credit_balance`, and `count_findings` tools, so your assistant can see your repositories, cost estimates, credit balance, and finding totals.
- New `list_pull_requests`, `get_pull_request`, and `start_pr_review` tools start reviews on GitHub, GitLab, Bitbucket, and Azure DevOps, and `get_pr_review_settings`, `update_pr_review_settings`, and `set_pr_reviews` change PR review settings.
- New `start_remediation`, `get_remediation`, and `get_automation_credit_balance` MCP tools let your AI assistant generate a fix pull request for a finding, follow it, and check automation credits.
- New MCP tools such as `list_context_documents`, `read_context_document`, `get_pentest_report`, `open_code_workspace`, `edit_context_document`, `update_threat_model`, and `create_application` let your agents read code and pentest reports, and edit threat models and applications.

## October 27, 2026

### Whitebox

- New [Scope step](/docs/whitebox/quickstart) in the wizard picks the folders a pentest covers, for GitHub, GitHub Enterprise Server, and public github.com repositories.

  ![Choose folders, where checked folders are included in the pentest](https://www.hacktron.ai/shots/whitebox/quickstart/whitebox_scope_folders/light.c6425c26.webp)

- New [attestation letters](/docs/whitebox/attestation-letters) give each customer a letter with a shareable link that opens without signing in, and a PDF.

  ![A sample attestation letter for Acme's Identity application, with the engagement dates, scope, methodology, retest confirmation, signature, and a verification QR code](https://www.hacktron.ai/shots/whitebox/attestation-letters/whitebox_attestation_public/light.8248ba45.webp)

- The wizard's last step is now a summary of your choices, such as **Source**, **Scope**, **Target**, and **Context**, each with **Edit**.
- Reports now list every deployed target and the accounts used to sign in.

### Review

- Pull requests with up to 500 changed files are now reviewed, up from 200.
- New **Post system comments** setting lets admins turn off notices about skipped reviews, usage limits, and configuration problems.
- Each developer now gets 50 free reviews per approved open source repository each cycle, up from 30.
- Auto-assignment now warns that bot authors take billable seats.

### Platform

- [People](/docs/review/people) now has separate **Members** and **Invitations** tabs.
- A finding's **Activity** tab now has a filter and a newest or oldest sort.
- [GitLab now works with Developer access](/docs/platform/repositories/gitlab) when your team adds the webhook and a `read_repository` deploy token.
- A GitLab connection can now be saved before setup is complete.
- The trial activation modal can now turn on reviews for every connected repository at once.

## October 21, 2026

### Whitebox

- [Retests](/docs/whitebox/retests) now start from **Request retest** on a completed scan, cover every finding except false positives and accepted risk.

  ![Retest result with a finding marked Verified fixed and the team's verification note](https://www.hacktron.ai/shots/whitebox/retests/whitebox_retest_result/light.32892a3a.webp)

- After a retest, **Download report** now offers the **Original scan** and **After retest** editions.
- With [dynamic testing](/docs/whitebox/quickstart), **Define target** now takes several apps, each with its own domain, **Auth instructions**, and **Verify access**, and **Verify all** checks them together.

- Organisation admins can now edit, verify, estimate, start, and stop their teammates' pentests.
- Report **Methodology** now gives how many functions each area selected, and **Coverage Detail** lists at most 50 entry points that no pass selected.

### Platform

- Every finding now shows an ID, such as `ACME-FD-12`, in its panel, on its full page, and in its URL, and clicking the ID copies it.
- A finding's **Activity** tab now lists each detection and every edit with who made it, and **Comments** shows only the thread.
- With a finding open, global search now leads with actions for it, such as **Change status**, **Change severity**, **Copy ID**, and **Copy link**.
- Pasting two or more finding IDs into the findings search now filters to those findings, and global search now finds a finding by its ID.
- The CWE badge on a finding now shows the weakness's full name on hover.
- [Repositories](/docs/platform/repositories) now warns when PR Review is on but no trial or subscription is active, with **Start free trial** for owners.
- Onboarding now connects GitHub, GitHub Enterprise Server, GitLab, Bitbucket, or Azure DevOps, and adds a **Choose your repositories** step.
- [Appliances](/docs/platform/on-premises) that cannot reach GitHub.com now disable its setup and name the cause, such as DNS or TLS.
- On appliances, the GitHub.com integration now shows webhook delivery health with **Send test**, and its PR reviews need a public HTTPS address.
- Dynamic testing is now on for every appliance.
- Appliances in managed pentest mode now show a cost estimate and a credit balance, and triage every pentest.

### API

- [List findings](/docs/api/findings/list-findings) now matches `repo_url` regardless of case, a trailing slash, or a `.git` suffix.

## October 9, 2026

### Whitebox

- The [pentest page](/docs/whitebox/logs) now has a collapsible **Timeline**, an **Agents** section that groups findings by agent, and a severity summary in its header.

  ::::tabs

  :::tab[Before]

  ![A completed pentest's page with every timeline step listed and the agents as coloured squares](https://www.hacktron.ai/shots/changelog/2026-10-09/pentest_page_before/light.af0be917.webp)

  :::

  :::tab[After]

  ![A completed pentest's page with the timeline collapsed and findings grouped under each agent](https://www.hacktron.ai/shots/changelog/2026-10-09/pentest_page_after/light.4439b702.webp)

  :::

  ::::

- [Full reports](/docs/whitebox/findings-and-reports) now have **Severity Rubric**, **Methodology**, **Coverage Detail**, and **Limitations and Disclaimer** sections, and their scope lists deployed targets and the testing window.

  ![Contents of a sample Full Whitebox Report: executive summary, scope, findings summary, methodology, severity rubric, individual findings, and limitations](https://www.hacktron.ai/shots/whitebox/findings-and-reports/whitebox_report_contents/light.f2ab593a.webp)

- A finding with live-validation evidence now gets a **Live Validation** section in the report.

### Platform

- The [Integrations](/docs/platform/integrations) page is now a searchable list with category tabs, and each integration opens in its own dialog.

  ::::tabs

  :::tab[Before]

  ![Integrations as a grid of cards, one per provider](https://www.hacktron.ai/shots/changelog/2026-10-09/integrations_before/light.06b84c8c.webp)

  :::

  :::tab[After]

  ![Integrations as a searchable list grouped into source code, issue tracking, and notifications](https://www.hacktron.ai/shots/changelog/2026-10-09/integrations_after/light.36257d3b.webp)

  :::

  ::::

- [Jira](/docs/platform/project-management/jira) now syncs finding status with linked issues in both directions, as [Linear](/docs/platform/project-management/linear) already did.
- Severity changes now update the priority of linked Jira and Linear issues.
- New **Update tickets from findings** and **Update findings from Jira** or **Linear** settings turn each sync direction on or off.
- Findings now have IDs such as `ACME-FD-12`, shown in Slack messages, Jira and Linear tickets, and pull request comments.
- A resolved finding that a later scan detects again now reopens, while false positives and accepted risks stay closed.
- New **Help** menu in the top bar links to the docs, the API reference, the MCP server, and the changelog.
- New **Send feedback** button in the sidebar sends a bug report or a suggestion to the Hacktron team.

### API

- [Finding endpoints](/docs/api/findings/get-finding) now accept a finding's ID, such as `ACME-FD-12`, in place of its UUID, and return it as `display_id`.

### MCP

- [Finding tools](/docs/mcp) now accept a finding's ID, such as `ACME-FD-12`, in place of its UUID.

## September 25, 2026

### Review

- [`@hacktronai review`](/docs/review/setup) on a commit that was already reviewed now replies with the result, or says the review is still running.
- A review you request with `@hacktronai review` now replies when it finds nothing.
- Scans with no findings no longer post a summary comment on GitLab, Bitbucket, or Azure DevOps pull requests.

### Platform

- [Repositories](/docs/platform/repositories) now shows **Repository**, **Owner**, **Findings**, **PR Scans**, and **Last Scan**, and repository access moves from its **Enabled** switch to each Git integration.
- [GitHub](/docs/platform/repositories/github) repositories added back to the GitHub App are now selected again automatically.
- [Appliances](/docs/platform/on-premises) can now review GitHub.com pull requests through a customer-owned GitHub App.

### API

- [List repositories](/docs/api/repos/list-repos) now returns `openFindingsCount` and `lastScanAt` for each repository.

## September 22, 2026

### Whitebox

- New [retests](/docs/whitebox/retests) send the findings you fixed and your fix details to the Hacktron team from **Retest findings**, and the PDF report shows each finding's outcome.
- New **Verify access** in the wizard tests your audit instructions and login credentials in a browser, with a **Live access preview**, before the pentest starts.
- New **View validation activity** on the pentest page streams what each validation agent does.

### Platform

- [People](/docs/review/people) search, filters, and sorting now cover every member, not only the first 100, and search also matches email and SCM usernames.
- Creating an organisation from the organisation menu now opens onboarding.
- Code in findings and reports now highlights Dart, Haskell, Erlang, and other languages the scan engine reads.

### API

- [Create scan](/docs/api/scans/create-scan) now treats a repository without `source` as `connected`.

## September 18, 2026

### Whitebox

- Pentests of GitLab repositories can now target a tag or a commit, not only a branch.
- PDF reports now number findings in display order, highlight code in the right language, and render Chinese, Japanese, and Korean text.
- Reports that state every finding was confirmed by hand now leave out findings marked false positive.

### Review

- Bot pull requests on GitHub, such as Dependabot and Renovate, are now reviewed when opened from a branch in the same repository, and take a [seat](/docs/review/people).
- When a later commit fixes a finding, Hacktron now replies and resolves its thread on GitLab, Bitbucket, and Azure DevOps, as on GitHub.
- New pushes to a pull request on GitLab, Bitbucket, or Azure DevOps are now reviewed from the last reviewed commit, as on GitHub.

### Platform

- Findings now show a CWE ID and a fix recommendation when the scan engine provides them.
- A finding's OWASP Top 10:2025 category can now be set or cleared from its menu.
- Global search now shows finding severity, finds people, and has **Quick actions** such as **Run Whitebox Scan** and **Review Highest-Priority Finding**.
- The **Application** filter on the **PR Review** tab of the [dashboard](/docs/platform/dashboard) now filters every widget, including the security score.
- A failed scan's page now shows why it failed.
- [Application](/docs/platform/context/applications) pages now open each repository's threat model in a side panel.
- Repositories renamed or moved on GitHub, GitLab, Bitbucket, or Azure DevOps now update in Hacktron.
- The [GitLab](/docs/platform/repositories/gitlab) integration now shows **Token expired** or **Token expiring**.
- Open fix pull requests from [Remediation](/docs/platform/automations/remediation) now close with a comment when the finding's fix lands on the base branch another way.
- [Appliances](/docs/platform/on-premises) now show their licence in organisation settings and warn 30 days before it expires.
- Appliances can now connect self-managed GitLab and review merge requests.
- Appliances can now edit a finding's title, description, severity, code, and proof of concept with **Edit finding**.

## August 19, 2026

### Review

- New **Post comments to source control** setting in [organisation settings](/docs/platform/organization-settings#post-comments-to-source-control) keeps finding details in Hacktron while checks still update.
- `@hacktronai review` now uses the pull request author's seat when the author is in your organisation, and the commenter's only for outside contributors.

### Platform

- The findings list and finding drawer are redesigned, with a **Category** column, status you can change in each row, and previous and next arrows in the drawer.

  ::::tabs

  :::tab[Before]

  ![A finding open in the drawer, with severity, file, and repository in a grid above the tabs](https://www.hacktron.ai/shots/changelog/2026-08-19/findings_drawer_before/light.d2a63e20.webp)

  :::

  :::tab[After]

  ![A finding open in the drawer, with severity and status in a header tray and previous and next arrows](https://www.hacktron.ai/shots/changelog/2026-08-19/findings_drawer_after/light.54153b22.webp)

  :::

  ::::
- [Billing](/docs/platform/billing) now shows **Whitebox Scan Credits** and **Automation credits** as separate accounts, each with its balance and use this period.
- Billing history now has **Product** and **Type** columns and lists credit purchases.
- Triage status now updates the linked [Linear](/docs/platform/project-management/linear) issue, and starting a fix moves it to **In Progress**.
- Azure DevOps pull request authors now appear in [People](/docs/review/people) and can hold Review seats, and triage replies and **Fix with AI** links now work on Azure DevOps.
- Members can now [connect a Microsoft account](/docs/platform/account-settings#connect-microsoft-for-azure-devops) so the Azure DevOps pull requests they open are attributed to them.
- An Azure DevOps connection can now store the token's expiry date, and Integrations warns before the token expires.
- **Account** and **Settings** are now one [Personal settings](/docs/platform/account-settings) page.
- Every member can now create, rename, rotate, and revoke their own API keys in **Org settings**.
- [Remediation](/docs/platform/automations/remediation) now opens fix pull requests on Azure DevOps.
- Merging a fix pull request into its target branch now resolves the finding and unblocks the check.
- A fix that no longer applies because the base branch changed now retries on its own, up to three times.
- Deleting an automation now asks for confirmation, and enabling an incomplete one says what is missing.
- Selecting findings now exports only the selected rows.
- An application's [threat model](/docs/platform/context/threat-models) now says when its repositories changed and asks you to regenerate it.
- Appliances can now reach an [internal Git host](/docs/platform/on-premises#allow-an-internal-git-host) that the operator allows, with its CA certificate.
- On-premises Whitebox pentests can now use enabled GitHub Enterprise Server repositories or uploaded `.zip`, `.7z`, `.tar.gz`, and `.tgz` archives up to 2 GiB.
- Appliances can now connect GitHub Enterprise Server through a GitHub App as well as a personal access token.

## August 3, 2026

### Whitebox

- Pasting a repository URL from your browser now fills in its branch, tag, or commit, and the wizard warns when it can't access the repository.
- A pentest in expert triage now shows **Validating findings before final results** until triage finishes.

### Review

- Replying `!fp`, `!accepted_risk`, or `!fixed` to a finding now resolves its [review thread](/docs/review/findings-feedback#triage-comments) on GitHub and GitLab.
- Author filters now accept [glob patterns](/docs/review/config#glob-pattern-syntax) in `.hacktron/config.yaml` and in organisation **Filters**.
- GitLab merge requests and Bitbucket pull requests opened by bots are now reviewed and take a seat, unless `exclude.authors` lists the bot.
- GitLab and Bitbucket reviews now count toward your organisation's [review pool](/docs/review/usage#pooled-review-limit), as GitHub reviews do.
- Bitbucket now supports `@hacktronai review`, and declining a pull request closes its findings.

### Platform

- New [Azure DevOps](/docs/platform/repositories/azure-devops) integration connects Azure DevOps Services or Server with an organisation URL and a personal access token, for Review and Whitebox.

  ![Connect Azure DevOps in Hacktron, with the organisation URL and token](https://www.hacktron.ai/shots/platform/repositories/azure-devops/azure_connect/light.6bf990d0.webp)

- New bulk triage changes the status or severity of the findings you select, or of every finding that matches your filters.
- Findings now show their category, and the findings list has a **Category** filter.
- The findings list now hides resolved findings by default.
- [Usage](/docs/review/usage) now has separate **PR Reviews**, **Automations**, and **Whitebox Scans** tabs.
- Automations now stop a run at the environment's credit cap, and an admin can raise the cap and start a new run.
- An Automations run now shows the agent's transcript live.
- Runs started with **Remediate** now appear in the Automations run history.
- A fix pull request onto a developer's branch now requests that branch's author as a reviewer.
- Organisations now get a one-time grant of 5,000 [Automation credits](/docs/platform/automations/credits) when they first pay for a subscription.

## July 15, 2026

### Whitebox

- New **Add expert human triage** at checkout has the Hacktron security team review every finding before you see it, for extra credits.
- The **Cost calculation** step now has a **Model** choice of **Default** or **Legacy**.
- Whitebox pentests can now use connected Bitbucket repositories.

### Review

- New `!fixed` [triage reply](/docs/review/findings-feedback#triage-comments) marks a finding resolved from a pull request comment or a Slack thread.
- [Repository configuration](/docs/review/config) now has `include` filters for labels, authors, branches, and title keywords, and `exclude` filters for authors and branches.
- The `skip` block in `.hacktron/config.yaml` is now `exclude`, and a `skip` block is ignored.
- New **Filters** in [organisation settings](/docs/platform/organization-settings#scan-filters) set default label, author, branch, and keyword filters, and a repository's config overrides each category it sets.
- Repositories no longer has a **PR Scan Branches** column, and branch filters now go in **Filters** or `.hacktron/config.yaml`.
- The pull request check now fails on blocking findings from earlier scans of the same pull request, not only the latest.
- On public GitHub repositories, a finding in a changed file with no changed line now posts as a file-level comment instead of in the redacted summary.

### Platform

- New [Bitbucket](/docs/platform/repositories/bitbucket) integration connects your workspaces, and Review scans their pull requests automatically.

  ![Select Bitbucket repositories in Hacktron](https://www.hacktron.ai/shots/platform/repositories/bitbucket/bitbucket_select_repositories/light.9ec116bd.webp)

- New [Automations](/docs/platform/automations) run Remediation on new findings that match a severity or repository rule, on the branches you pick, and notify Slack or email.

  ![The Settings tab with a trigger for Critical and High findings, an action, and a Slack notifier](https://www.hacktron.ai/shots/platform/automations/automation_settings/light.b4efacef.webp)

- New **Remediate** on a finding has [Remediation](/docs/platform/automations/remediation) open a fix pull request.
- Findings now [export](/docs/whitebox/findings-and-reports#export-findings) as CSV, SARIF, or JSON from **Export** on the findings list, with your current filters applied.

- Taint findings now open in an annotated code reader that steps from source to sink.
- The findings list now opens newest first, with false positives and closed findings hidden.
- [Slack](/docs/platform/communication-apps/slack) finding messages now have **Mark Resolved** in their menu.
- New [Automation credits](/docs/platform/automations/credits) on **Billing** pay for Automations runs, with auto top-up.

### API

- New [`GET /findings/export`](/docs/api/findings/export-findings) exports findings as CSV, JSON, or SARIF and takes the same filters as `GET /findings`, including `repo_url`.

## June 23, 2026

### Review

- On public repositories, Review now leaves out the title, description, proof of concept, and location of [findings outside the diff](/docs/review/findings-feedback) and links to each one in Hacktron instead.
- GitHub pull request reviews now say when Hacktron has built or refreshed the repository's threat model.

### Platform

- New [Context](/docs/platform/context) page lists your repositories and applications with their threat models and documents, which Review and Whitebox use as context.
- New [threat models](/docs/platform/context/threat-models) for each repository are built from reviews, triage, and your documents, and keep your edits when they regenerate.

  ![A threat model open for editing, with Cancel and Save](https://www.hacktron.ai/shots/platform/context/threat-models/threat_model_edit/light.73a64779.webp)

- New [applications](/docs/platform/context/applications) group repositories under one merged threat model, and a pentest can target an application.

  ![The New application dialog, with a name and the repositories to include](https://www.hacktron.ai/shots/platform/context/applications/new_application/light.1e4b56d6.webp)

- Context documents now accept `.txt` files and PDFs of up to 50 pages, and **Add Context** adds them to repositories or applications.
- New [**Single sign-on (SSO)**](/docs/platform/security-settings) button on the sign-in page signs you in through your organisation's SAML or OIDC identity provider.
- Findings can now be filtered by **Application**.
- A finding's detail panel now links to its pull request.

### API

- New [dependency firewall endpoints](/docs/api/hfw/get-package-verdict) check packages against Hacktron's known-malware feed, one at a time or in a batch, with no API key.

## June 18, 2026

### Whitebox

- A pentest of an uploaded archive is now named after the archive.

### Review

- A check that `fail_on.severity` failed now [turns back to passing](/docs/review/findings-feedback) on GitHub and GitLab once you mark its blocking findings as false positives or accepted risks, and fails again if you reopen one.

### Platform

- New **Mark as duplicate** closes a finding as a [duplicate](/docs/review/findings-feedback) of another in the same repository, and unmarking reopens it.

- The [dashboard](/docs/platform/dashboard) scan volume chart is now **Scan volume across time**, with stacked daily bars and Review and Whitebox counts on hover.

### API

- [`PATCH /findings/{id}`](/docs/api/findings/update-finding) now accepts `duplicate_of` to mark or unmark a duplicate.

### MCP

- The [`update_finding`](/docs/mcp) tool now accepts `duplicate_of` to mark or unmark a duplicate.

## June 15, 2026

### Review

- [`.hacktron/config.yaml`](/docs/review/config) can now skip a review when every changed file matches `skip.paths`, or when the title or labels match `skip.keywords` or `skip.labels`.
- New [`fail_on.severity`](/docs/review/config) setting in `.hacktron/config.yaml` fails the GitHub check or GitLab commit status when a finding is at or above that severity.

### Platform

- New [multi-factor authentication](/docs/platform/account-settings) protects your account with an authenticator app and backup codes.

- New [**Require MFA for members**](/docs/platform/security-settings) setting makes every member of the organisation set up MFA.
- The findings **Scan** filter now takes several scans, and the **Repository** and **Scan** filters narrow each other.

### MCP

- New [MCP server](/docs/mcp) lets AI assistants list, read, and triage your scans and findings, signing in with OAuth or an API key.

## June 11, 2026

### Review

- Connecting a [GitLab](/docs/platform/repositories/gitlab) project now turns on merge request reviews, as connecting a GitHub repository does.
- The Review trial and onboarding now treat a connected GitLab account the same as GitHub.

## June 10, 2026

### Whitebox

- The cost estimate now names the languages in a repository that Hacktron does not support yet, instead of failing without a reason.

### Review

- [Free trials](/docs/review/billing) no longer need a credit card.
- Findings on a pull or merge request closed without merging now move to **Closed**, and return when it reopens, with any triage kept.

### Platform

- [Slack](/docs/platform/communication-apps/slack) finding cards now have a **Fix with AI** button that shows the fix prompt and opens it in Cursor or Claude.
- The **Connect GitLab** dialog now walks through [GitLab's group service account setup](/docs/platform/repositories/gitlab) step by step.

## June 7, 2026

### Whitebox

- A [pentest](/docs/whitebox/quickstart) can now target a tag or commit instead of a branch, for connected GitHub repositories and public URLs.

### Review

- [GitLab merge request comments](/docs/review/findings-feedback) now match GitHub, with severity badges, a collapsible proof of concept, trace diagrams, and a **Fix with AI** block.
- Replying `!fp`, `!valid`, or `!accepted_risk` to a merge request comment now triages the finding, as on GitHub.
- [`@hacktronai review`](/docs/review/setup) now starts a review on GitLab merge requests, and replaces `@hacktron review` on GitHub.

### Platform

- [GitHub Enterprise Server](/docs/platform/repositories/github-enterprise-server) now connects through a GitHub App registered on your server, so Review works there as well as Whitebox.

- Triage from the web app or Slack now appears in the finding's pull request or merge request thread.
- [Jira](/docs/platform/project-management/jira) ticket creation now searches large projects and assignee lists, and new issues link back to the finding.

## June 3, 2026

### Review

- [Review limits](/docs/review/usage) are now pooled across the organisation, 50 reviews for each active developer seat, instead of 50 per seat.
- New [**Usage**](/docs/review/usage) page shows owners the organisation's review pool, each developer's reviews, spillover reviews, and the estimated cost.

  ![The Usage page, with the Organization review pool above the Overage billing card](https://www.hacktron.ai/shots/review/usage/overage_billing_usage/light.019e9632.webp)

- **Spillover billing** has moved from Billing to the Usage page.
- Approved open source repositories now get 50 reviews per developer for each repository each billing period, up from 30.

### Platform

- [Connecting GitHub](/docs/platform/repositories/github) without admin rights in the GitHub organisation now sends an installation request, and the integration appears once an admin approves it.
- [Jira](/docs/platform/project-management/jira) setup now starts with **Automatically create tickets** turned on.
- The [shared Slack channel](/docs/platform) with the Hacktron team is now offered to every owner with a work email, without a trial or subscription.

## June 1, 2026

### Whitebox

- Pentests are now called **Whitebox Scans** in the app, PDF reports, and emails.

### Review

- Anyone with write access can now comment [`@hacktron review`](/docs/review/integrations/github-gitlab) to review a pull request on demand, including drafts and external contributors' pull requests, on the commenter's seat.
- GitHub pull request comments now show severity badges instead of emoji.
- The **Fix with AI** prompt in pull request comments now asks for a reproduction, a root-cause fix, and a regression test.

### Platform

- The sidebar now has collapsible **Configuration** and **Management** sections that stay as you left them, and account actions are in its header.
- The full-page finding view now has the panel's status and severity controls, **Copy as Markdown**, and **Create Ticket**.

## May 26, 2026

### Whitebox

- New **Executive Report** under **Download Report** is a pentest summary PDF with a risk rating, a severity summary, and the top 10 findings.

### Review

- [GitLab](/docs/platform/repositories/gitlab) merge requests on GitLab.com and self-hosted GitLab can now be reviewed, with findings on the merge request and a commit status.
- A finding that repeats an earlier one is now linked to it, and its pull request comment shows **Duplicate of:** with a link to the original.
- Hacktron now reacts with a thumbs-up to a pull request comment when it accepts the triage command in it.

### Platform

- New **Create on Jira** on a finding files a [Jira](/docs/platform/project-management/jira) ticket, with the project, issue type, labels, assignee, and priority editable first.
- Jira settings now set a default project, issue type, labels, and assignee, a severity to priority mapping, and **Automatically create tickets**.
- Comments and status changes on a finding from the web app, the API, or a GitHub pull request now post as replies in its [Slack](/docs/platform/communication-apps/slack) thread.
- Signup can now connect GitLab with **Use GitLab instead**.

## May 19, 2026

### Review

- Admins can now restart a failed or stopped pull request review with **Restart**.
- **PR Reviews** now shows each pull request's number.

### Platform

- The [dashboard](/docs/platform/dashboard) now has **Overview**, **PR Review**, and **Whitebox Scan** tabs.
- New **Affected Code Flow** tab on a finding shows its taint trace from source to sink, or a call graph when there is no trace.
- [Linear](/docs/platform/project-management/linear) tickets can now go to a **Default project**, with a priority that follows the finding's severity.
- Moving a Linear issue to a completed state now resolves its finding, and moving it out reopens the finding.
- New **Backfill existing findings** in Linear settings creates tickets for approved findings that have none.
- New **Resolution health** on the dashboard shows the mean time to resolve and SLA compliance for each severity.
- New **SLA Thresholds** in [settings](/docs/platform/organization-settings) set the resolution days and target for each severity.
- The **PR Review** tab now shows a security score from 0 to 100, with a banner when it drops below your **Security Score Threshold**.
- New **Export** on the dashboard downloads the open tab as a PDF.
- Findings can now open on their own page with **Open in full page**.

## May 16, 2026

### Review

- New **Spillover billing** setting lets owners on a paid plan keep [reviews running past the per-seat limit](/docs/review/usage), billed as overage.
- Searching **PR Reviews** now matches pull request numbers.

## May 15, 2026

### Whitebox

- Public pentest pages now show the pentest's timeline, agents, and findings.

## May 13, 2026

### Review

- Each developer seat now includes [50 pull request reviews](/docs/review/usage) per billing period, and reviews stop at the limit until the next period.
- A pull request now counts once against the limit, however often it is pushed.
- Approved open source repositories now have their own limit of 30 reviews per developer each billing period.
- New **Skip trial** on [Billing](/docs/review/billing) ends a trial early and starts the paid plan.
- New **Resubscribe** on Billing restarts a cancelled subscription and restores its seats.
- Running pull request reviews can now be cancelled with **Cancel**.
- Pull request comments now show that `!fp` and `!accepted_risk` take an optional reason.
- Open Source Program applications now get an email confirming they were received.

### Platform

- Owners with a work email and a trial or subscription can now create a [shared Slack channel](/docs/platform) with the Hacktron team, at signup or in settings.
- The **Scan** column in Findings now links to the pull request or pentest.

## May 4, 2026

### Review

- New open source program gives approved open source repositories free pull request reviews.
- Hacktron now adds a 👀 reaction to a pull request while it reviews it, and leaves 👍 when it finds nothing.
- Closing a pull request without merging now cancels its review.
- The **Code Review** page is now called **PR Reviews**.

### Platform

- New **Triage Comment** button on Hacktron's Slack finding cards sets a status and adds a comment in one step.

  ![A Triage Comment dialog in Slack, with a status and a comment for the finding](https://www.hacktron.ai/shots/review/integrations/slack/slack_triage_comment/light.eaa7ce42.webp)

- New **Getting started** checklist walks owners and admins through setting up pentests and code review, and members through linking GitHub.
- [Slack](/docs/review/integrations/slack) can now be linked under **Account** > **Connected accounts**, and triage actions in Slack require it.
- You can now change or set your password under [**Account**](/docs/platform/account-settings) > **Security**.

## April 23, 2026

### Review

- New [**Code Review**](/docs/review) page lists pull request reviews, each linked to its pull request.
- Pull request reviews now show the pull request's author under **Created by**, not the person who installed the GitHub App.

### Platform

- **Findings** now lists pentest and pull request findings together, with a **Scan** filter and column.
- Affected code in a finding is now syntax-highlighted.
- A finding's status and severity can now be changed from its card in Slack.
- Admins can now change the organisation's URL slug in **Organization Settings**.

### API

- New [list repositories](/docs/api/repos/list-repos) endpoint returns your repositories and whether pull request reviews are on for each.

## April 20, 2026

### Whitebox

- New **Context documents** step in the **Run Pentest** wizard adds [context documents](/docs/platform/context), such as a threat model, from your library or as new Markdown uploads.
- The person who starts a pentest now gets an email when it completes, fails, or finishes triage, and **Email notifications** in **Settings** turns these off.
- PDF reports now draw each finding's trace as a diagram.

### Review

- Pull request comments now link to the finding in Hacktron.

### Platform

- Finding and scan links shared in [Slack](/docs/platform/communication-apps/slack) now unfurl with live status and severity.
- Findings now have **Create Ticket** > **Create on Linear**, which files a Linear issue with the finding's details.
- [Linear](/docs/platform/project-management/linear) now has a **Default team** setting and an **Automatically create tickets** toggle.
- [Billing](/docs/platform/billing) now handles your payment method, billing details, invoices, and cancellation in the app, and buys pentest credits with the card on file.

### API

- New [REST API](/docs/api) at `api.hacktron.ai` runs pentests, estimates their cost, and lists, exports, and updates scans and findings, with interactive docs at `api.hacktron.ai/docs`.
- New **API Keys** section in **Organization Settings** creates [API keys](/docs/api/authentication) with **Read only** or **Read & Write** access and an optional expiry.

## April 6, 2026

### Whitebox

- The **Run Pentest** wizard can now test a **Public URL** or an **Upload archive** (ZIP, 7Z, or TAR.GZ), as well as **Connected repos**.
- Admins can now run pentests and buy credits, not only owners.
- Pentests whose findings are being triaged now show **Triaging**, not **Pending**.

### Platform

- Findings now show a **Trace** diagram of how the vulnerability moves through your code.
- You can now connect more than one [GitHub](/docs/platform/repositories/github) organisation with **Add GitHub organization**.
- Comments in a finding's **Activity** now render Markdown, with **Write** and **Preview** tabs.
- New [**Organization Settings**](/docs/platform/organization-settings) page lets admins rename the organisation.

## March 23, 2026

### Whitebox

- A pentest's page now shows a notice while its findings are being triaged.
- The live pentest page now shows why each dismissed finding was dismissed.

### Platform

- Findings now have an [**Activity**](/docs/review/findings-feedback) thread with comments and status changes from the web app, Slack, and GitHub.
- Changing a finding's status now asks for an optional reason.
- New **Copy as Markdown** button copies a finding as a Markdown report.

## March 18, 2026

### Whitebox

- New live page for a running pentest shows its [timeline](/docs/whitebox/logs), findings as agents validate them, and the agents at work.
- New **Cost estimation** step in the **Run Pentest** wizard estimates the credits a pentest needs before you start.
- New **Download PDF Report** button on a pentest generates a [PDF report](/docs/whitebox/findings-and-reports) of its findings.
- A pentest can now cover more than one repository.
- New **Pentests** tab in **Billing** buys [pentest credits](/docs/whitebox/billing) with **Buy credits**.
- Pentests can now be saved as drafts and resumed later.

### Review

- Dev seats are now called [**Code Review seats**](/docs/review/billing).
- Free trials now have no seat limit, with up to 200 pull request reviews per seat.
- After a trial ends, auto-assignment now stops at 50 seats, up from 10.
- A new push to a pull request is now reviewed only for the changes since the previous push.
- Pull request comments now have an **Open in Claude** button next to **Open in Cursor**.

### Platform

- New **Promotion code** field in **Billing** applies a Stripe promotion code to your subscription.
- You can now leave an organisation with **Leave organization** in the user menu.

## March 1, 2026

### Whitebox

- Pentests are now paid for with [pentest credits](/docs/whitebox/billing), bought through Stripe at the **Checkout** step of the **Run Pentest** wizard.

### Review

- Pull request comments now have an **Open in Cursor** button that opens a fix prompt in Cursor.

## February 18, 2026

### Review

- New [per-seat billing](/docs/review/billing) with a 14-day free trial: a **Dev seat** covers one developer's pull requests and a **Sec seat** covers the CLI and VS Code extension.
- [People](/docs/review/people) can now assign Dev seats automatically as developers open pull requests, up to a seat limit you set.
- New **PR Scan Branches** setting in **Repositories** limits a GitHub repository's pull request reviews to up to two target branches.
