Public: anyone can read this; the crew can change it.
/advisories: the forge listens to CVE.org, OSV, GHSA, NVD, CISA KEV and EPSS, matches them to every repo's dependencies, and gives a sleek explorer with fix-pull actions, MCP tools and integrations #6017
This is a first slice of #6005, not the whole issue. /advisories now works for ingested OSV and CISA KEV data and shows which repos are hit. The forge doesn't listen to any feed yet, and most of the rest of the issue's list is still to do.
stopped parked by the crew deploy d46897c
4 earlier comments
This is a first slice of #6005, not the whole issue. /advisories now works for ingested OSV and CISA KEV data and shows which repos are hit. The forge doesn't listen to any feed yet, and most of the rest of the issue's list is still to do.
tsc is clean, the new tests pass, and forge-looks, mcp-size and reserved-names pass. In the wider run of related test files, two capture tests in test/looks.test.ts fail because the sandbox can't run chromium. I did not run the full suite or check. The run also showed openapi-coverage: 29 NOT_YET_DESCRIBED entries could be removed; I did not look into it.
What changed
src/core/advisories.tsparses OSV JSON, one record or an array, into one row per package range. It rejects malformed input, caps a batch at 500 records, and validates ids and versions.- The CISA KEV list marks which CVEs are exploited in the wild. The
advisoryandadvisory_kevtables are an additive migration. src/core/exposure.tsreads each repo'spackage-lock.jsonat its default branch. Parsing is cached per blob id, and the same module matches the packages against the advisories./advisoriesis for forge admins who are people; anyone else gets a 404. The top line answers "am I exposed today?". Cards show the KEV badge, severity, ecosystem and package, fixed version, and "affects N of your repos". There is a search box, and exploited advisories sort first.- An admin pastes OSV or KEV JSON into a form on the page to ingest it (
POST /advisories, same-origin checked). Output is escaped. - MCP:
audittakes anadvisories: "<text>"argument that returns the same data.tools/listis at its size ceiling, so I extendedauditinstead of adding a tool, asdocs/MCP.mdsays to do. I added a short note todocs/MCP.md. forge.jsonlists/advisoriesinapp.looks;advisoriesis a reserved name.- Tests:
test/advisories.test.tsandtest/advisories-page.test.ts. They cover version comparison, parsing, KEV ordering, lockfile exposure, escaping, the 404 for non-admins and the cross-origin 403.
Left out
- Live listening to CVE.org, OSV, GHSA, NVD, KEV and EPSS. Ingest is paste-in for now; a poller would call
parseOsvandsaveKev. - EPSS and CVSS numeric scoring; severity is whatever OSV supplies.
- Lockfiles other than npm's
package-lock.json. Dependency paths and SBOM export are not built. - The fix-pull, accept-risk, mute and not-reachable actions.
- Paging the owner, streaming the feed, filters beyond text search, and trends.
- Push, email and webhook notifications, the RSS/Atom feed, and the scratchpad board view.
Try it: sign in as an admin and open /advisories. Paste an OSV record with the feed set to "OSV record(s)", then the KEV JSON. Or call the MCP audit tool with advisories: "lodash". No dependencies were added.
This comment needs no code change, so I pushed nothing new. It's an automatic triage note. It says #6005 has no pillar and waits behind the Later gate until someone names one. Naming a pillar is a planning decision for a person to make on the issue, so I haven't tried to set one.
The branch scout/6005-advisories-the-forge-listens-to-cve-org still holds the first slice from the previous push:
- OSV and CISA KEV ingest
- per-repo lockfile exposure
- the admin
/advisoriespage - the
audittool'sadvisoriesargument
The live feed listeners, fix-pull actions, notifications, RSS feed and board view are still unbuilt. They could be split into child issues once a pillar is chosen.
I merged main into the branch and pushed it. The only conflict was src/http/mcp.ts. I ran the advisories tests, the mcp-size test and the type check, and they pass. The full bun test did not finish in this sandbox, so the forge's check will be its first full run.
- Conflict:
mainsplitmcp.tsinto one file per tool undersrc/http/mcp/tools/. I tookmain's version ofmcp.tsand moved this pull'sauditchange intosrc/http/mcp/tools/audit.ts. That change is theadvisoriesargument, still limited to an admin who is a person, and it still answers withadvisoryView. - Size ceiling: on the merged tree the
mcp-sizetest failed, becausemainwas already close to thetools/listargument-description budget. I gaveadvisoriesno description and droppedaudit's duplicaterepodescription, whichREPO_ARGalready supplies.docs/MCP.mdstill documents the argument.
I merged main into this branch and pushed. The only conflict was in docs/MCP.md.
- Conflict: both sides had edited the end of the MCP docs. I kept main's line saying the CLI
forgecommand covers "tell, status, decide, plan, preview, pulls", and kept the Advisories section after it. - Checks: a targeted run passed, 45 tests across 11 files. It covered the advisories, advisories page, audit and first eight
mcp-*suites. - Not done: I didn't get a result from a full
bun testplus type check; it ran past 15 minutes in the background. The forge's own check on this push will run all of it.
Parked by the crew: the check stayed red through 2 automatic tries
This is a first slice of #6005, not the whole issue.
/advisoriesnow works for ingested OSV and CISA KEV data and shows which repos are hit. The forge doesn't listen to any feed yet, and most of the rest of the issue's list is still to do.tscis clean, the new tests pass, andforge-looks,mcp-sizeandreserved-namespass. In the wider run of related test files, two capture tests intest/looks.test.tsfail because the sandbox can't run chromium. I did not run the full suite orcheck. The run also showedopenapi-coverage: 29 NOT_YET_DESCRIBED entries could be removed; I did not look into it.What changed
src/core/advisories.tsparses OSV JSON, one record or an array, into one row per package range. It rejects malformed input, caps a batch at 500 records, and validates ids and versions.advisoryandadvisory_kevtables are an additive migration.src/core/exposure.tsreads each repo'spackage-lock.jsonat its default branch. Parsing is cached per blob id, and the same module matches the packages against the advisories./advisoriesis for forge admins who are people; anyone else gets a 404. The top line answers "am I exposed today?". Cards show the KEV badge, severity, ecosystem and package, fixed version, and "affects N of your repos". There is a search box, and exploited advisories sort first.POST /advisories, same-origin checked). Output is escaped.audittakes anadvisories: "<text>"argument that returns the same data.tools/listis at its size ceiling, so I extendedauditinstead of adding a tool, asdocs/MCP.mdsays to do. I added a short note todocs/MCP.md.forge.jsonlists/advisoriesinapp.looks;advisoriesis a reserved name.test/advisories.test.tsandtest/advisories-page.test.ts. They cover version comparison, parsing, KEV ordering, lockfile exposure, escaping, the 404 for non-admins and the cross-origin 403.Left out
parseOsvandsaveKev.package-lock.json. Dependency paths and SBOM export are not built.Try it: sign in as an admin and open
/advisories. Paste an OSV record with the feed set to "OSV record(s)", then the KEV JSON. Or call the MCPaudittool withadvisories: "lodash". No dependencies were added.Closes #6005