@bitgo/blake2b
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
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): Stable BitGo org transfer, unchanged for years, no malicious diff. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Part of same legitimate transfer, long-settled. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Publisher change stale for 1463d, consistent with legitimate transfer not takeover. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in test.js is decoding known BLAKE2b test vectors; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.2.4 | 2 / 1 | |
| 3.2.3 | 2 / 1 | |
| 3.2.2 | 2 / 1 | |
| 3.2.1 | 2 / 1 | |
| 3.2.0 | 2 / 1 | |
| 3.0.4 | 2 / 1 | |
| 3.0.3 | 2 / 1 | |
| 3.0.2 | 2 / 1 | |
| 3.0.1 | 2 / 1 | |
| 3.0.0 | 2 / 1 |
v3.2.3
2 findingsThis version was published by a different npm account (zahin-mohammad) than the most recent previously approved version (tylerlevine) on 2023-07-28. It has since remained available on npm for 1089 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.
v3.2.2
2 findingsThis version was published by a different npm account (mmcshinsky-bitgo) than the most recent previously approved version (tylerlevine) on 2023-07-18. It has since remained available on npm for 1099 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.
v3.2.1
2 findingsThis version was published by a different npm account (mmcshinsky-bitgo) than the most recent previously approved version (tylerlevine) on 2022-11-29. It has since remained available on npm for 1330 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.
v3.2.0
2 findingsThis version was published by a different npm account (bitgoaaron) than the most recent previously approved version (tylerlevine) on 2022-10-18. It has since remained available on npm for 1372 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.
v3.0.4
2 findingsThis version was published by a different npm account (mmcshinsky-bitgo) than the most recent previously approved version (tylerlevine) on 2022-09-30. It has since remained available on npm for 1390 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.
v3.0.3
2 findingsThis version was published by a different npm account (mmcshinsky-bitgo) than the most recent previously approved version (tylerlevine) on 2022-07-19. It has since remained available on npm for 1463 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.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.