Passive by default
Start with scan results only. No code changes are made during the recommended first onboarding run.
LegacyFixer
LegacyFixer scans selected Python repositories, records dependency-security results, and creates review-ready pull requests only when repository settings explicitly allow it.
Start with scan results only. No code changes are made during the recommended first onboarding run.
When enabled, fixes are proposed through isolated branches and pull requests for human review.
Each repository controls whether PR creation is enabled and how many LegacyFixer PRs can be open.
LegacyFixer is available through controlled access for selected public Python repositories. It is not an open self-serve product yet.
To request access, use the branded contact address that will be published before public onboarding opens. Include one repository you would be comfortable testing in a controlled maintenance workflow.
requirements.txtnested requirements.txtpoetry.lockPipfile.locksetup.cfg install_requirespassive findingsdependency conflictdependency hellPR diff granularityno PR in passive modeBest first fit: a small or medium public repository that is not production-sensitive.
Review a real passive LegacyFixer scan before requesting access. The demo shows the recommended first onboarding path: scan, record findings, and avoid pull request creation until the result is reviewed.
Open read-only passive status page Successful scan with findings and no PR opened