Quarantine for your dependencies.
Lazaret inspects code before it reaches your build: your own project, and every package it pulls from npm and PyPI. It flags injection bugs, leaked secrets, hidden install-time payloads, and versions with known vulnerabilities.
pip install lazaret
Python 3.10 or later. Nothing else gets installed.
A lazaret was the harbor station where arriving ships and cargo were held and inspected before they could enter port. Ships in quarantine flew a yellow flag.
| Package | Verdict | Finding |
|---|---|---|
| npm:left-pad@1.3.0 | OK | |
| npm:colors-extended@2.0.1 | SUSPICIOUS | SC-EVAL-DECODE decodes and runs hidden code on install |
| pypi:requests@2.32.3 | OK | |
| pypi:fastcsv-tools@0.4.0 | WARN | S-SECRET hardcoded credential in the published package |
What it checks
- Your code
- About 58 rules for Python, JavaScript and SQL, with taint tracking that follows untrusted input across functions and files into SQL, shell and template sinks. Reports as HTML, JSON, or SARIF for code scanning, with a quality gate for CI.
lazaret .- Published packages
- Downloads npm and PyPI archives, scans them in memory without unpacking anything to disk, and gives each version a verdict. Catches decode-then-execute tricks, packed and obfuscated JavaScript, install hooks, and smuggled binaries.
lazaret-registry scan npm:left-pad- Installed dependencies
- Matches the npm and PyPI packages actually installed or pinned in a project against a CVE bundle, and fails the build on versions with known-exploited vulnerabilities.
lazaret-sca . --bundle cve-bundle.json- Code your AI assistant writes
- An MCP server lets Claude and other assistants scan a snippet before writing it to disk, or check the files they just changed.
lazaret-mcp
Nothing to trust but the standard library
A supply-chain tool with dependencies is itself a supply-chain risk. Lazaret has none. It runs on Python's standard library alone, builds without downloading anything, and its whole test suite runs on a stock interpreter.
Releases are built reproducibly and published from CI with signed attestations, so any file on PyPI can be traced to the exact commit and workflow that produced it. This page loads no scripts, fonts, or anything else from third parties.