← Home

jsml

npm Repository

Appendable sequences of JSON documents

4
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

pvorb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Package is 13+ years old; 0.0.0 versioning was common in early npm ecosystem. Named author, real repo, and inbound dep edges confirm legitimacy. ai
bogus-package bogus-package AI (bogus-package): Tiny, no-dep, no-keyword profile is consistent with a minimal early-era utility library from 2011, not spam or malware. ai

Versions (showing 4 of 4)

Version Deps Published
0.1.1 0 / 0
0.1.0 0 / 0
0.0.1 0 / 0
0.0.0 0 / 0

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.1

1 finding
LOW No provenance attestation provenance

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

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