June 2026

​

Findings

• Stable finding identity: A finding keeps its identity across scans, multi-repo scans, and moved code, so its status and history carry over. See Re-scans and fix detection.
• Descriptions in rows: Each finding row shows a short description.

​

Pull requests

• Check overrides: Mark as passed or Mark as failed on the GitHub check. The check shows who overrode it.
• Reorganized settings: General, Pull Requests (Merge Requests on GitLab), Preferences, and Code Settings.

​

Bug fixes

• Dismissed findings: No longer come back as new.
• Fixed status: Set only after a successful update.
• GitLab: Vulnerability sync and ticket links to the source scan are reliable.

​

Scanning

• Fix detection: Every deep scan re-verifies your open findings and marks the ones fixed in the code as Fixed, with an explanation and the fixing commit. See Re-scans and fix detection.

​

Findings

• Adjust severity: Set a finding’s CVSS score from 0 to 10 with a slider. The new severity syncs to linked tickets. See Findings.
• Data-flow viewer: See how input reaches the vulnerable code.

​

Scanning

• PHP: Gecko analyzes PHP codebases.

​

Pull requests

• Richer PR comments: Comments include each finding’s details.

​

Bug fixes

• Invitations: Invitations and email verification work reliably.