← Home

version-guard

npm Repository Homepage

Used to ensure modern CLI scripts fail silently on old js versions. Useful for static analysis tools and similar

7
Versions
0BSD
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

voxpelli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is the intentional core behavior of version-guard — it loads package.json from a caller-supplied path to inspect the Node version. Not an arbitrary code execution risk. ai
bogus-package bogus-package AI (bogus-package): README link-dump signal is a false positive for a utility package documenting ecosystem usage. No keywords is a minor omission, not a spam/phishing indicator for this established package. ai

Versions (showing 7 of 7)

Version Deps Published
1.1.3 0 / 9
1.1.2 0 / 18
1.1.1 0 / 19
1.1.0 0 / 19
1.0.2 0 / 19
1.0.1 0 / 19
1.0.0 0 / 18

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.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.