and if you don't want to run a registry, there's omni-audit.
it's an open-source cli we built, written in go and mit licensed.
it doesn't check cves, because that's what the registry already does.
it looks for what cve scanners miss: packages published as malware, typosquatting, dependency confusion and insecure registry configs.
works with npm and composer projects, and runs in github actions.
https://github.com/omni-line/omni-audit
btw, for anyone who doesn't know omni line yet.
it's a self-hosted package registry for npm and composer.
it sits between your projects and packagist or npmjs.
every package your ci installs goes through it, gets cached, and gets scanned for known vulnerabilities.…
GitHubGitHub - omni-line/omni-audit: 🛡️ A fast, zero-config CLI to audit your projects for Dependency Confusion and supply chain risks across multiple registries. Backed by Omni Line.🛡️ A fast, zero-config CLI to audit your projects for Dependency Confusion and supply chain risks across multiple registries. Backed by Omni Line. - omni-line/omni-audit
commit 6991b34