jspm-npm
jspm npm endpoint
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of crisptrutski with no new maintainer added, published by the long-standing trusted author guybedford. Consistent with routine maintainer cleanup, not a takeover signal for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Addition of crisptrutski by trusted publisher guybedford with no code changes; consistent with legitimate team expansion for this long-established jspm package. | ai | |
| phantom-deps | phantom-dep:rmdir | AI (phantom-deps): Phantom dependency pattern is expected in jspm registry packages; rmdir is referenced in config but not directly imported. | ai | |
| phantom-deps | phantom-dep:systemjs-builder | AI (phantom-deps): Phantom dependency pattern is expected in jspm registry packages; systemjs-builder is referenced in config but not directly imported. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (tar, glob, rsvp, resolve) are all well-established packages consistent with jspm-npm's functionality. Publisher guybedford has a strong track record; no malicious signal. | ai | |
| dependencies | unvetted-dep:request | AI (dependencies): The `request` package was a standard HTTP library widely used in the npm ecosystem; this is a legitimate dependency for this era of jspm tooling. | ai | |
| provenance | no-provenance | AI (provenance): jspm-npm is a long-established package from a highly reputable publisher; lack of Sigstore provenance is expected for this publishing workflow. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.29.6 | 12 / 4 | |
| 0.28.12 | 11 / 4 | |
| 0.28.2 | 11 / 4 | |
| 0.27.2 | 11 / 4 | |
| 0.26.8 | 11 / 4 | |
| 0.26.2 | 11 / 4 | |
| 0.26.1 | 11 / 4 | |
| 0.21.2 | 9 / 0 | |
| 0.20.0 | 9 / 0 | |
| 0.15.0 | 9 / 0 | |
| 0.14.2 | 9 / 0 | |
| 0.14.0 | 9 / 0 | |
| 0.13.3 | 8 / 0 | |
| 0.11.0 | 7 / 0 | |
| 0.10.0 | 7 / 0 | |
| 0.8.5 | 7 / 0 | |
| 0.7.0 | 6 / 0 | |
| 0.3.0 | 6 / 0 | |
| 0.1.1 | 4 / 0 |
v0.29.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 finding[Accepted risk] 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[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.