1.1Coming
Package-registry checks
A dependency the model invented is refused.
Product / Lanes / Security lane
Security laneComing
Scans that run themselves, fixes you approve.
The first fully autonomous lane: scheduled route audits, dependency scans and secret scans become findings in chat, then a fix pull request that waits for you.
Fig.1 · sample
open findings1
scan 1scan 14
02:00 scheduled run · no one started it
route audit 2 routes read workspace_id from body
osv scan 1 high · lodash 4.17.20
secret scan 1 token · .env.example:12 (value hidden)
fix PR #231 opened · waiting for your approval
How it works.
- 01 /
Scheduled scan
Route-auth audit, dependency CVEs and secrets, with no one starting it.
- 02 /
Findings in chat
De-duplicated, with file, line and type; secret values never shown.
- 03 /
Fix PR
A proposed fix through the factory line, for your approval.
What you get. Each point labelled with its real status.
1.2Coming
Severity as rules
What notifies you at once lives in a decision table.
1.3Coming
Never merges its own PR
The lane proposes; you decide.
1.4Coming
Injected failures show as unknown
A broken scanner is reported as unknown, never as clean.