← Home

mono-vir

npm Repository Homepage
10
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

electrovir

Keywords

monorepomonorepomono-repobuildnpmtoolingfor each

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established package with clean history; lack of provenance is common and not a risk signal here. ai
phantom-deps phantom-dep:@augment-vir/assert AI (phantom-deps): Declared runtime dep used in config/type context; stable false positive for this package. ai
publish-pattern dormant-publish AI (publish-pattern): Publisher has strong track record (295/0); no material changes from prior version; low-risk monorepo tooling package. ai
phantom-deps phantom-dep:tsx AI (phantom-deps): tsx is listed as a runtime dep in package.json and used as a script runner; phantom-dep heuristic false positive for this package. ai

Versions (showing 10 of 10)

Version Deps Published
2.5.0 7 / 35
2.4.3 7 / 35
2.4.2 7 / 35
2.4.1 7 / 35
2.4.0 7 / 35
2.2.2 6 / 35
2.2.1 6 / 35
2.2.0 6 / 35
2.1.0 6 / 35
2.0.7 6 / 35

v2.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.