jspm
Import Map Package Manager
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): guybedford is the canonical jspm author/creator with a long established track record (2190 approved packages, 4751 days). The transition back to this account is legitimate. | ai | |
| phantom-deps | phantom-dep:cac | AI (phantom-deps): cac is a declared runtime dependency used in the bundled CLI output; phantom detection is a false positive for bundled packages. | ai | |
| phantom-deps | phantom-dep:rollup | AI (phantom-deps): rollup is a declared runtime dependency used in the bundled output; phantom detection is a false positive for bundled packages. | ai | |
| phantom-deps | phantom-dep:@jspm/generator | AI (phantom-deps): jspm is a bundled CLI tool; dependencies are compiled into dist/ rather than directly imported at runtime. | ai | |
| source-diff | encoded-string-file:dist/cli.js | AI (source-diff): The encoded string is a base64-encoded WebAssembly binary (wasm-bindgen output). The AGFzbQ prefix confirms WASM magic bytes. This is a standard pattern for shipping compiled WASM in a JS CLI bundle. | ai | |
| phantom-deps | phantom-dep:@jspm/plugin-rollup | AI (phantom-deps): jspm is a bundled CLI tool; dependencies are compiled into dist/ rather than directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): jspm is a bundled CLI tool; dependencies are compiled into dist/ rather than directly imported at runtime. Phantom dep findings are false positives for this package. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): jspm is a bundled CLI tool; dependencies are compiled into dist/ rather than directly imported at runtime. | ai |
Versions (showing 51 of 179)
| Version | Deps | Published |
|---|---|---|
| 4.5.0 | 5 / 14 | |
| 4.4.0 | 5 / 14 | |
| 4.3.0 | 5 / 14 | |
| 4.2.0 | 5 / 14 | |
| 4.1.5 | 5 / 14 | |
| 4.1.4 | 5 / 14 | |
| 4.1.3 | 5 / 14 | |
| 4.1.2 | 5 / 14 | |
| 4.1.1 | 5 / 14 | |
| 4.1.0 | 5 / 14 | |
| 4.0.3 | 5 / 14 | |
| 4.0.2 | 5 / 14 | |
| 4.0.1 | 5 / 14 | |
| 4.0.0 | 5 / 14 | |
| 3.3.5 | 5 / 9 | |
| 3.3.4 | 5 / 10 | |
| 3.3.3 | 5 / 10 | |
| 3.3.2 | 5 / 10 | |
| 3.3.1 | 5 / 10 | |
| 3.3.0 | 5 / 10 | |
| 3.2.0 | 5 / 10 | |
| 3.1.2 | 5 / 10 | |
| 3.1.1 | 5 / 10 | |
| 3.1.0 | 5 / 10 | |
| 3.0.2 | 4 / 10 | |
| 3.0.1 | 4 / 10 | |
| 3.0.0 | 4 / 10 | |
| 0.16.55 | 20 / 3 | |
| 0.16.54 | 20 / 3 | |
| 0.16.53 | 20 / 3 | |
| 0.16.52 | 20 / 3 | |
| 0.16.51 | 20 / 3 | |
| 0.16.50 | 20 / 3 | |
| 0.16.49 | 20 / 3 | |
| 0.16.48 | 20 / 3 | |
| 0.16.47 | 20 / 3 | |
| 0.16.46 | 20 / 3 | |
| 0.16.45 | 20 / 3 | |
| 0.16.44 | 20 / 3 | |
| 0.16.43 | 20 / 3 | |
| 0.16.42 | 20 / 3 | |
| 0.16.41 | 20 / 3 | |
| 0.16.40 | 20 / 3 | |
| 0.16.39 | 20 / 3 | |
| 0.16.38 | 20 / 3 | |
| 0.16.37 | 20 / 3 | |
| 0.16.36 | 20 / 3 | |
| 0.16.35 | 20 / 3 | |
| 0.16.34 | 20 / 3 | |
| 0.16.33 | 20 / 3 | |
| 0.16.32 | 20 / 3 |
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
3 findingsThis version was published by a different npm account than previous versions on 2026-03-02. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-09-09. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
2 findingsThis version was published by a different npm account than previous versions on 2024-07-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-08-15. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.