Checked on every pull request. Scanned every week. Free.
On by default · Nothing to set up · No credit card needed
The Malicious Package Guard checks every npm and PyPI package a pull request adds, with or without a review. It never blocks unless you choose.
Direct and transitive, with the dependency that pulls them in.
parse-args 1.2.0via cli-kitMalicious versions, lookalike names and AI-invented packages.
expresssnew nameA new npm package, or an update that adds an install script, is flagged before it runs on your machine or in CI.
postinstallnewWorkflow files get the same scrutiny as your code.
pull_request_target use.github/workflows/deploy.yml steps:+ - uses: some-org/deploy-action@mainSupply chainCI workflow
Unpinned actionA branch can point at new code at any time. Pin the action to a full commit SHA.
Each repository is scanned as soon as you add it: every dependency and every workflow.
No setup.Then weekly by default, against the latest advisories. Only new findings open an issue.
No repeats.Admins can switch a repository to daily, or turn its scan off.
Per repository.Nothing comes out of your balance.
Checks whether your code actually calls the affected functions or code paths.
Runs only when an advisory names a package you use.
On a public repository, malware details stay off the pull request, so whoever planted the package isn’t tipped off.