jsprim
utilities for primitive JavaScript types
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Stale publisher change, stable 1720d on npm, not a takeover pattern. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature stable package; dormancy reflects low churn, not compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Known joyent maintainer roster added, consistent with legitimate org handoff. | ai | |
| dependencies | unvetted-dep:verror | AI (dependencies): verror is a well-known Joyent error-handling library; its use in jsprim is expected and stable across versions. | ai | |
| dependencies | unvetted-dep:extsprintf | AI (dependencies): extsprintf is a well-known Joyent sprintf library; its use in jsprim is expected and stable across versions. | ai | |
| dependencies | unvetted-dep:assert-plus | AI (dependencies): assert-plus is a widely-used assertion library; its use in jsprim is expected and stable across versions. | ai |
v2.0.1
2 findingsThis version was published by a different npm account (bahamat) than the most recent previously approved version (dap) on 2021-11-03. It has since remained available on npm for 1720 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.