← Home

litesvm

npm
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

kheaveyaursen

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): Standard napi-rs musl detection pattern; stable across versions. ai
semgrep semgrep:child-process-execsync AI (semgrep): Runs 'ldd --version' only to detect musl; fixed command, not user-controlled. ai
semgrep semgrep:dynamic-require AI (semgrep): napi-rs NAPI_RS_NATIVE_LIBRARY_PATH override pattern; standard for native bindings. ai
phantom-deps phantom-dep:bs58 AI (phantom-deps): Declared runtime dep used transitively; stable false positive for this package. ai
phantom-deps phantom-dep:fastestsmallesttextencoderdecoder AI (phantom-deps): Declared runtime dep used transitively; stable false positive for this package. ai

Versions (showing 10 of 10)

Version Deps Published
1.0.0 3 / 17
0.8.0 2 / 18
0.7.0 2 / 18
0.6.0 2 / 18
0.5.0 2 / 18
0.4.0 2 / 18
0.3.3 3 / 19
0.3.2 3 / 19
0.3.1 3 / 19
0.3.0 3 / 19

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.8.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.

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.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.

v0.5.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.

v0.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.

v0.3.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.

v0.3.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.

v0.3.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.

v0.3.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.