Skip to content

Release Note #1 (2026.05)

You can now invite, view, and remove users from your organization in the new user management area.

Managing GitHub connections now requires an organization admin role.

The triage import and export option is no longer available. Existing triage data is unaffected.

  • Fixed markdown export of findings.
  • Fixed several triage status display issues.

You can now remove a GitHub connection from the Connections page when you no longer need it.

The Connections page now lists organization access requests that are waiting for approval, so you can track them alongside your active connections.

Reproduction Steps and remediation restored

Section titled “Reproduction Steps and remediation restored”

Reproduction Steps and remediation guidance are visible again on the finding detail view.

Triage events on a finding now show which user made the change, giving you a clearer audit trail.

  • Fixed an error when completing a GitHub connection installation that returned without a state token.

Inactive connections handled at the project level

Section titled “Inactive connections handled at the project level”

If a GitHub connection becomes inactive, the affected project surfaces the state clearly so you know which projects need a working connection before you can scan.

Navigating to the marketing site from the app now sends you to the correct destination.

Connect a GitHub account or organization and start scans on your repos, with no manual upload needed.

The new Connections page lets you add and manage several connections side by side.

The scan-creation flow now remembers your progress. Refreshing or stepping away mid-setup no longer resets you to step one.

Triage uses an updated set of status values. Existing triage events were migrated automatically.