The lockfile is where most scanners stop. It is where Vulnesis starts.
Six places a dependency comes from
- Manifests and lockfiles: Read across every supported ecosystem. A lockfile gives exact versions rather than ranges, so the answer is what resolves.
- The package tree on disk: node_modules, site-packages, vendor, the Cargo registry, the local Maven repository and their equivalents are read directly. A package that is installed but not declared is reported as exactly that.
- CI configuration: Install commands in GitHub Actions, GitLab CI, CircleCI, Azure Pipelines, Buildkite, Jenkins and dozens more. Tooling installed by the pipeline is part of the build even though it appears in no manifest.
- Shell, Makefile and task recipes: A bare apt-get or pip install line in a build script has no manifest anywhere near it. It still puts software on the machine that produces your artefact.
- Images and package databases: Base images, Compose services, Kubernetes pod templates and Helm charts, plus the installed package database inside an image root filesystem.
- Compiled artefacts: Go build info, Rust cargo auditable data and JVM archive coordinates recovered from binaries that ship with no manifest at all.
36 ecosystems, including npm, PyPI, Conda, Go, Cargo, Deno, RubyGems, Maven, Gradle, sbt, Clojars, NuGet, Conan, vcpkg, Bazel, Swift PM, CocoaPods, Carthage, Pub, Hex, Cabal, Stack, Julia, opam, Composer, CRAN, Zig, Nix, Helm, Terraform, Docker, GitHub Actions.
The records that decide urgency, on every package
4 KEV catalogues
CISA, ENISA, Vulnesis and VulnCheck.
20 exploit sources
Exploit maturity from proof of concept to weaponised, with EPSS and Coalition ESS.
EOL end-of-life records
Runtimes and packages past support, as their own queue.
MAL malware and scorecards
Known malicious packages, typosquats and OpenSSF Scorecard.
Is the vulnerable function ever called?
The CLI builds a call graph with tree-sitter and walks it from your entry points to the vulnerable symbol named in the advisory. A dependency you never call the affected code path of is a finding you can close with evidence rather than an argument. The surface is shown either way, including when the verdict is unreachable, so a reviewer can check the working.
The queries are served per vulnerability, across 17 languages, and your source never leaves the machine. Unreachable verdicts become VEX evidence. How reachability is computed · Read the announcement
Upgrade to the closest clean version
Every published version of a dependency is scored on vulnerabilities, exploits, malware and end of life, and the closest clean version is recommended. Choose the safest, latest, stable or rolling preset, and the Package Firewall applies the same answer at install time.
$ vulnetix fix --dry-run
Seven ways to fail a build, and none of them are on by default
Combine the gates that match your risk appetite. An organisation policy can raise them for everyone, and when it does the organisation value wins even over an explicit flag, so a team cannot quietly opt out of a standard. Quality gate
--severity: Fail on any finding at or above a severity.--exploits: Fail on known exploitation, weighted by how the exploit is evidenced.--block-malware: Fail when a dependency is a known malicious package.--block-eol: Fail when a runtime or package has passed its end of life date.--block-unpinned: Fail when a dependency resolves through a range rather than a pin.--version-lag: Fail when a dependency is more than N major versions behind.--cooldown-days: Fail on releases younger than N days, which is where compromised versions live.
One round trip, one document
Parsing happens locally. Package names and versions go out, and a CycloneDX document comes back enriched with advisories, exploit intelligence, end of life records and remediation advice. Existing findings and VEX statements in the document are carried forward rather than overwritten.
CycloneDX 1.7, SPDX 2.3, SARIF, OpenVEX, CSAF VEX
Stop it at install time
The Package Firewall refuses malware and exploitable versions before a byte downloads, and malscan checks the bytes already on disk. Package Firewall · Malscan