Erydas
How you engage
Three steps. Stop after any of them.
Look never changes the tree. Propose opens a pull request and waits. Prove runs only inside a disposable environment that cannot publish.
01 · Look
See what is installed and what is exposed
You do
- Run eridas scan on a lockfile, or paste a public URL in the Scan workspace.
- Choose a level. Level 2 is the default live scan: headers plus leaked files and secrets in bundles.
- Read the report. Exit 1 means disclosed findings remain. That is not a clean tree.
Erydas may
- Inventory package-lock.json lockfile versions 2 and 3.
- Query OSV for those exact versions.
- Run a passive GET-only recon of a public URL.
- Store the scan and show it beside older runs.
Hard stop
- Does not run npm install or lifecycle scripts.
- Does not rewrite package.json or the lockfile.
- Does not delete findings for the repository.
- Refuses private, loopback, and metadata addresses.
- Refuses pnpm and Yarn instead of guessing their trees.
Always in force
- OSV decides what is disclosed. Erydas does not invent advisories.
- package-lock.json decides what is installed. A stale lockfile is an error.
- A person decides whether anything changes. There is no silent push to the default branch.
- Older findings stay. The current view is the latest succeeded scan.
- One organization cannot read another organization's jobs, events, or grants.