LegacyFixer
Public scan example
A verified historical result from a passive scan, showing what LegacyFixer records before any pull request is enabled.
Historical, read-only example
This is a snapshot of a controlled LegacyFixer run completed on June 10, 2026, not a live scan. Repository identifiers and sensitive diagnostic output are intentionally omitted. The actual self-service application requires GitHub sign-in to protect each workspace's data.
Open the working LegacyFixer application (GitHub sign-in required)
Recorded scan result
- Run
- #88
- Scan date
- 2026-06-10
- Status
- success
- Result
- NO_ACTION
- Reason
- passive_findings
- Pull requests opened
- 0
- Dependency findings
- 23 reported
- Affected packages
- 1
The worker completed this passive scan and recorded dependency findings. NO_ACTION refers to no remediation being performed, not to an absence of security findings.
Explore the recorded findings
Dependency audit — 23 vulnerabilities reported
The scan reported 23 known vulnerabilities in one affected package: django==5.2.11. At the time, available fix-version candidates included 5.2.13, 5.2.14, and 5.2.15. This historical result does not represent current vulnerability or remediation status.
Repository and execution context
The validation repository used a non-standard default branch, main-616. LegacyFixer detected that branch, ran the passive dependency audit, and persisted the result. The recorded execution lasted 1 minute 50 seconds.
Why no pull request was opened
This repository was configured for passive scanning. Findings were recorded, but automatic remediation was not authorized. When enabled per repository, LegacyFixer can instead propose a fix through a reviewable pull request; it does not auto-merge.
Try LegacyFixer with your own repository
Sign in with GitHub, choose the repositories to connect, and review scan outcomes in your private workspace. The free trial lasts 7 days and supports up to 3 connected repositories.