HomeProduct
Know what your dependencies bring in.
Every pentest checks the npm and PyPI packages your code depends on and flags the malicious and risky ones. Package rules let you decide what is allowed in.
Part of every pentest.
Read the dependencies
During a pentest, Nullgap reads the npm and PyPI packages the repository depends on.
Flag what’s wrong
Packages that are malicious, or risky enough to need a look, are flagged with the reason.
Set your rules
Block or allow packages, require a minimum age, decide on install scripts and pick the registries you trust.
Flagged packages, and rules to keep them out.
| Rule | What it does | Example |
|---|---|---|
| Block | Flag a package whenever it appears | a known-bad package name |
| Allow | Accept a package you have reviewed | an internal fork |
| Minimum age | Flag versions newer than the age you set | a release published yesterday |
| Install scripts | Flag packages that run scripts when installed | a postinstall hook |
| Registries | Flag packages from registries you haven’t approved | an unknown mirror |
Scope and limits.
- npm and PyPI
- Packages from the npm and PyPI ecosystems are checked.
- During a pentest
- Malicious and risky packages are flagged as part of a whitebox pentest.
- Rules you control
- Block, allow, minimum age, install scripts and registries, set for your workspace.
- Flagged, not proven
- A risky package is a flag for your review. Exploitable code paths go through the full proof like any other finding.
Works with
Supply-chain questions
Which ecosystems are covered?
npm and PyPI.
Does it cost extra?
No. Supply-chain checks run during every pentest.
What is a minimum age rule?
It flags package versions published more recently than the age you choose, which gives the community time to spot a bad release.
Get your first proof today.
Connect a repository and watch Nullgap find, prove and fix. You only ever see what it could prove.
Free 14-day trial · No card · or book a demo with a security engineer