SupplyChainChecker Exposure intelligence
SOFTWARE SUPPLY CHAIN SECURITY

Know what your
dependencies know.

Upload a project archive and get a focused, evidence-based scan for known compromised packages and supply-chain exposure.

Drop your project here

We inspect manifests, lockfiles and installed package metadata. Your archive is processed temporarily and deleted after the scan.

⌁

A clean scan starts
with the right files.

Prepare a ZIP of the project you want to review. The scanner reads dependency metadata only; it does not install or run the uploaded project.

01

Include these files

Keep the dependency manifests and lockfiles that describe the project.

package.jsonpackage-lock.json · yarn.lockpnpm-lock.yaml · bun.lockbrequirements.txtpyproject.toml · uv.lockpoetry.lock · Pipfile.lock
02

Optional, but useful

Include installed dependencies when you want stronger evidence about what was actually installed.

node_modules/Python site-packages/*.dist-info/METADATAPKG-INFO
03

Leave these out

Protect sensitive data and keep the upload focused and lightweight.

.env · credentials · private keys.git/ · cache foldersbuild/ · dist/ · coverage/Large media and unrelated binaries
SUPPORTED TODAY JavaScript / npm Python / PyPI Project files only Go modules, container images and GitHub Actions are not supported yet.