bitcoinjs-message
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Long-standing org transfer from dcousens to junderw, stable for years. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Old, stable publisher change; not indicative of takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): bech32 is a legitimate encoding dep needed for segwit address support. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex literal '0014' is a standard SegWit script opcode prefix; not a payload. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding Bitcoin signatures is core library functionality, not obfuscation. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 6 / 5 | |
| 2.1.4 | 6 / 5 | |
| 2.1.3 | 6 / 5 | |
| 2.1.2 | 6 / 5 | |
| 2.1.1 | 6 / 5 | |
| 2.1.0 | 6 / 5 | |
| 2.0.0 | 5 / 5 |
v2.1.4
2 findingsThis version was published by a different npm account (junderw) than the most recent previously approved version (dcousens) on 2020-12-23. It has since remained available on npm for 2036 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.1.3
2 findingsThis version was published by a different npm account (junderw) than the most recent previously approved version (dcousens) on 2020-09-04. It has since remained available on npm for 2147 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.1.2
2 findingsThis version was published by a different npm account (junderw) than the most recent previously approved version (dcousens) on 2020-09-04. It has since remained available on npm for 2147 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.1.1
2 findingsThis version was published by a different npm account (junderw) than the most recent previously approved version (dcousens) on 2020-06-17. It has since remained available on npm for 2225 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.1.0
2 findingsThis version was published by a different npm account (junderw) than the most recent previously approved version (dcousens) on 2019-06-16. It has since remained available on npm for 2593 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. Only ~12% of npm packages have provenance, so this is common but not ideal.