arweave
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Webpack globalThis polyfill boilerplate, not dynamic code exec of user input. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher matched to known maintainer by email per provenance INFO finding. | ai | |
| dependencies | unvetted-dep:arweave-asn1 | AI (dependencies): Publisher's own asn1.js fork used consistently by the official arweave-js library. | ai | |
| npm-metadata | url-dep:arweave-asn1 | AI (npm-metadata): Longstanding GitHub dep for asn1.js fork; stable pattern for this package. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in pem.js is standard RSA key encoding logic for a blockchain crypto library, not payload obfuscation. Stable false positive for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in pem.js is standard PEM/ASN.1 key handling for a crypto library. No malicious payload; stable false positive for this package. | ai |
Versions (showing 59 of 59)
| Version | Deps | Published |
|---|---|---|
| 1.15.7 | 4 / 24 | |
| 1.15.5 | 4 / 24 | |
| 1.15.3 | 4 / 24 | |
| 1.15.1 | 4 / 24 | |
| 1.15.0 | 4 / 24 | |
| 1.14.4 | 4 / 24 | |
| 1.14.1 | 4 / 24 | |
| 1.14.0 | 4 / 24 | |
| 1.13.8 | 4 / 24 | |
| 1.13.7 | 4 / 24 | |
| 1.13.6 | 4 / 24 | |
| 1.13.5 | 4 / 24 | |
| 1.13.4 | 4 / 24 | |
| 1.13.3 | 4 / 24 | |
| 1.13.1 | 4 / 24 | |
| 1.13.0 | 4 / 24 | |
| 1.12.7 | 4 / 24 | |
| 1.12.6 | 4 / 24 | |
| 1.12.4 | 4 / 24 | |
| 1.12.3 | 4 / 24 | |
| 1.12.2 | 6 / 25 | |
| 1.12.1 | 6 / 25 | |
| 1.12.0 | 6 / 25 | |
| 1.11.9 | 6 / 24 | |
| 1.11.8 | 6 / 24 | |
| 1.11.7 | 6 / 24 | |
| 1.11.6 | 6 / 24 | |
| 1.11.1 | 6 / 22 | |
| 1.10.23 | 6 / 22 | |
| 1.10.22 | 6 / 22 | |
| 1.10.21 | 5 / 23 | |
| 1.10.20 | 5 / 23 | |
| 1.10.19 | 5 / 23 | |
| 1.10.18 | 5 / 23 | |
| 1.10.17 | 5 / 23 | |
| 1.10.16 | 5 / 23 | |
| 1.10.15 | 5 / 23 | |
| 1.10.14 | 5 / 23 | |
| 1.10.13 | 4 / 23 | |
| 1.10.11 | 4 / 23 | |
| 1.10.10 | 4 / 23 | |
| 1.10.9 | 4 / 23 | |
| 1.10.8 | 4 / 23 | |
| 1.10.7 | 4 / 23 | |
| 1.10.6 | 4 / 23 | |
| 1.10.5 | 4 / 18 | |
| 1.10.4 | 4 / 20 | |
| 1.10.3 | 4 / 17 | |
| 1.10.2 | 4 / 17 | |
| 1.10.1 | 4 / 17 | |
| 1.10.0 | 4 / 17 | |
| 1.9.1 | 4 / 17 | |
| 1.2.0 | 4 / 14 | |
| 1.1.8 | 4 / 12 | |
| 1.1.5 | 4 / 12 | |
| 1.1.3 | 4 / 11 | |
| 1.1.2 | 4 / 11 | |
| 1.1.0 | 4 / 11 | |
| 1.0.1 | 4 / 11 |
v1.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rosmcmahon) than the most recent previously approved version (mcmonkeys1) on 2023-01-26, but rosmcmahon is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.12.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rosmcmahon) than the most recent previously approved version (mcmonkeys1) on 2023-01-06, but rosmcmahon is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.12.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rosmcmahon) than the most recent previously approved version (mcmonkeys1) on 2023-01-06, but rosmcmahon is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.12.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rosmcmahon) than the most recent previously approved version (mcmonkeys1) on 2023-01-06, but rosmcmahon is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rosmcmahon) than the most recent previously approved version (mcmonkeys1) on 2022-11-30, but rosmcmahon is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rosmcmahon) than the most recent previously approved version (mcmonkeys1) on 2022-11-27, but rosmcmahon is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rosmcmahon) than the most recent previously approved version (mcmonkeys1) on 2022-08-14, but rosmcmahon is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rosmcmahon) than the most recent previously approved version (mcmonkeys1) on 2022-06-02, but rosmcmahon is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.10.23
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rosmcmahon) than the most recent previously approved version (mcmonkeys1) on 2022-01-03, but rosmcmahon is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.10.22
2 findingsThis version was published by a different npm account (rosmcmahon) than the most recent previously approved version (mcmonkeys1) on 2021-12-28. It has since remained available on npm for 1664 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.
v1.10.21
2 findingsThis version was published by a different npm account (rosmcmahon) than the most recent previously approved version (mcmonkeys1) on 2021-12-28. It has since remained available on npm for 1664 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.
v1.10.20
2 findingsThis version was published by a different npm account (rosmcmahon) than the most recent previously approved version (mcmonkeys1) on 2021-12-28. It has since remained available on npm for 1664 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.
v1.10.19
2 findingsThis version was published by a different npm account (rosmcmahon) than the most recent previously approved version (mcmonkeys1) on 2021-12-23. It has since remained available on npm for 1669 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.
v1.10.18
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mcmonkeys1) than the most recent previously approved version (cedriking) on 2021-10-12, but mcmonkeys1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.10.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mcmonkeys1) than the most recent previously approved version (cedriking) on 2021-03-15, but mcmonkeys1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.