What is Provenix?¶
Provenix is a firewall for your npm dependencies. It's an npm-compatible
registry that your developers and CI install from instead of
registry.npmjs.org. Behind it, Provenix fetches packages from the public
registry (and any private registries you add), scans them, and serves only
the versions your team has approved.
What it promises¶
- Unreviewed versions are never installed. Every install fetches package metadata and tarballs through Provenix. A version that hasn't been approved isn't in the metadata your client sees, and its tarball isn't served.
- You keep building. While a new version is held, installs keep resolving the last approved version. Approved packages stay installable even when the upstream registry is down.
- You can see the evidence. For every held version, a reviewer can see why it was held: scan findings, a score, and what changed since the previous approved version.
- Decisions are recorded. A reviewer can approve, reject or emergency-bypass a version with a reason. Every decision lands in an audit log that can't be edited.
Who does what¶
App teams (developers and CI pipelines) change only their registry
settings and a token. Day to day, they meet Provenix in two places: a
package that isn't approved yet, which fails with a 451, and a new version
that's held while their builds keep using the previous one.
Reviewers work the quarantine queue in the Provenix console, a few times a day. They read scan findings and decide.
Workspace admins register clients, seed approved baselines for existing projects, and write policy (how long versions are held, which scores auto-approve, which versions are denied outright).
Supported clients¶
Provenix is tested with npm, Yarn (classic and Berry) and pnpm. See Configure npm, Yarn and pnpm for the versions covered and the settings each one needs.
Next¶
See how a package moves through Provenix: How Provenix works.