← Home

jspm

npm

Import Map Package Manager

100
Versions
Apache-2.0
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

guybedfordjkrishna

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 100 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
0.16.31 20 / 3
0.16.30 20 / 3
0.16.29 20 / 3
0.16.28 20 / 3
0.16.27 20 / 3
0.16.26 20 / 3
0.16.25 20 / 3
0.16.24 20 / 3
0.16.23 20 / 3
0.16.22 20 / 3
0.16.21 20 / 3
0.16.20 20 / 3
0.16.19 20 / 3
0.16.18 20 / 3
0.16.17 20 / 3
0.16.16 20 / 3
0.16.15 19 / 3
0.16.14 19 / 3
0.16.13 19 / 3
0.16.12 19 / 3
0.16.11 19 / 3
0.16.10 19 / 3
0.16.9 19 / 3
0.16.8 19 / 3
0.16.7 19 / 3
0.16.6 19 / 3
0.16.5 19 / 3
0.16.4 19 / 3
0.16.3 19 / 3
0.16.2 19 / 3
0.16.1 19 / 3
0.16.0 19 / 3
0.15.7 19 / 3
0.15.6 19 / 3
0.15.5 19 / 3
0.15.4 19 / 3
0.15.3 19 / 2
0.15.2 19 / 2
0.15.1 19 / 2
0.15.0 19 / 2
0.14.0 17 / 1
0.13.4 17 / 1
0.13.3 17 / 1
0.13.2 17 / 1
0.13.1 17 / 1
0.13.0 17 / 1
0.12.0 17 / 1
0.11.6 17 / 1
0.11.5 17 / 1
Showing 100 of 179 Next page →

v4.5.0

1 finding
LOW No provenance attestation provenance

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

v4.4.0

3 findings
HIGH Publisher changed: jkrishna → guybedford (on 2026-03-02) provenance

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

HIGH Long encoded string in modified file: dist/cli.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v4.3.0

2 findings
HIGH Publisher changed: guybedford → jkrishna (on 2026-02-02) provenance

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

LOW No provenance attestation provenance

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

v4.2.0

1 finding
LOW No provenance attestation provenance

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

v4.1.5

1 finding
LOW No provenance attestation provenance

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

v4.1.4

1 finding
LOW No provenance attestation provenance

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

v4.1.3

1 finding
LOW No provenance attestation provenance

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

v4.1.2

1 finding
LOW No provenance attestation provenance

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

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.0

1 finding
LOW No provenance attestation provenance

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

v4.0.3

1 finding
LOW No provenance attestation provenance

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

v4.0.2

1 finding
LOW No provenance attestation provenance

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

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v4.0.0

2 findings
HIGH Publisher changed: jkrishna → guybedford (on 2025-05-19) provenance

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

LOW No provenance attestation provenance

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

v3.3.5

1 finding
LOW No provenance attestation provenance

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

v3.3.4

1 finding
LOW No provenance attestation provenance

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

v3.3.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: guybedford → jkrishna (on 2024-09-09) provenance

[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 finding
LOW No provenance attestation provenance

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

v3.3.1

2 findings
HIGH Publisher changed: jkrishna → guybedford (on 2024-07-22) provenance

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

LOW No provenance attestation provenance

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

v3.3.0

1 finding
LOW No provenance attestation provenance

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: guybedford → jkrishna (on 2023-08-15) provenance

[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 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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