@bitgo/sdk-coin-hash
BitGo SDK coin library for Provenance
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher with SLSA provenance is a security improvement, consistent with BitGo CI migration. | ai | |
| source-diff | obfuscated-file:dist/test/unit/utils.js | AI (source-diff): Standard tsc-compiled test file; long lines are test data strings. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): All handles (old and new) are BitGo org accounts; this is an internal team rotation, not a hijack. | ai | |
| source-diff | obfuscated-file:dist/test/resources/hash.js | AI (source-diff): Long lines are base64-encoded test vectors in compiled TypeScript output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/hash.js | AI (source-diff): Standard tsc-compiled test file; long lines are test data strings. | ai | |
| source-diff | obfuscated-file:dist/test/unit/hashToken.js | AI (source-diff): Standard tsc-compiled test file; long lines are test data strings. | ai | |
| source-diff | obfuscated-file:dist/test/unit/keyPair.js | AI (source-diff): Standard tsc-compiled test file; long lines are test data strings. | ai | |
| source-diff | obfuscated-file:dist/src/hashToken.js | AI (source-diff): Standard tsc-compiled source file; long lines are token config arrays. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/contractCallBuilder.js | AI (source-diff): Standard tsc-compiled test file; long lines are test data strings. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/StakingActivateBuilder.js | AI (source-diff): Standard tsc-compiled test file; long lines are test data strings. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/StakingDeactivateBuilder.js | AI (source-diff): Standard tsc-compiled test file; long lines are test data strings. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/StakingWithdrawRewardsBuilder.js | AI (source-diff): Standard tsc-compiled test file; long lines are test data strings. | ai | |
| source-diff | obfuscated-file:dist/test/unit/tokenTransaction.js | AI (source-diff): Standard tsc-compiled test file; long lines are test data strings. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transaction.js | AI (source-diff): Standard tsc-compiled test file; long lines are test data strings. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/transactionBuilder.js | AI (source-diff): Standard tsc-compiled test file; long lines are test data strings. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/transferBuilder.js | AI (source-diff): Standard tsc-compiled test file; long lines are test data strings. | ai | |
| phantom-deps | phantom-dep:@bitgo/sdk-lib-mpc | AI (phantom-deps): Same-org transitive dep used indirectly via abstract-cosmos; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@cosmjs/encoding | AI (phantom-deps): Declared as a direct dep in package.json; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 96 of 96)
| Version | Deps | Published |
|---|---|---|
| 3.9.26 | 8 / 3 | |
| 3.9.25 | 8 / 3 | |
| 3.9.23 | 8 / 3 | |
| 3.9.22 | 8 / 3 | |
| 3.9.21 | 8 / 3 | |
| 3.9.20 | 8 / 3 | |
| 3.9.19 | 8 / 3 | |
| 3.9.18 | 8 / 3 | |
| 3.9.17 | 8 / 3 | |
| 3.9.16 | 8 / 3 | |
| 3.9.15 | 8 / 3 | |
| 3.9.14 | 8 / 3 | |
| 3.9.13 | 8 / 3 | |
| 3.9.12 | 8 / 3 | |
| 3.9.11 | 8 / 3 | |
| 3.9.10 | 8 / 3 | |
| 3.9.9 | 8 / 3 | |
| 3.9.8 | 8 / 3 | |
| 3.9.7 | 8 / 3 | |
| 3.9.6 | 8 / 3 | |
| 3.9.5 | 8 / 3 | |
| 3.8.8 | 8 / 3 | |
| 3.6.0 | 8 / 3 | |
| 3.5.2 | 8 / 3 | |
| 3.5.1 | 8 / 3 | |
| 3.5.0 | 8 / 3 | |
| 3.4.1 | 8 / 3 | |
| 3.4.0 | 8 / 3 | |
| 3.3.1 | 8 / 3 | |
| 3.3.0 | 8 / 3 | |
| 3.2.1 | 8 / 3 | |
| 3.2.0 | 8 / 3 | |
| 3.1.11 | 8 / 3 | |
| 3.1.10 | 8 / 3 | |
| 3.1.9 | 8 / 3 | |
| 3.1.8 | 8 / 3 | |
| 3.1.7 | 8 / 3 | |
| 3.1.6 | 8 / 3 | |
| 3.1.5 | 8 / 3 | |
| 3.1.4 | 8 / 3 | |
| 3.1.3 | 8 / 3 | |
| 3.1.2 | 8 / 3 | |
| 3.1.1 | 8 / 3 | |
| 3.1.0 | 8 / 3 | |
| 3.0.52 | 8 / 3 | |
| 3.0.51 | 8 / 3 | |
| 3.0.50 | 8 / 3 | |
| 3.0.49 | 8 / 3 | |
| 3.0.48 | 8 / 3 | |
| 3.0.47 | 8 / 3 | |
| 3.0.46 | 8 / 3 | |
| 3.0.45 | 8 / 3 | |
| 3.0.44 | 8 / 3 | |
| 3.0.43 | 8 / 3 | |
| 3.0.42 | 8 / 3 | |
| 3.0.41 | 8 / 3 | |
| 3.0.40 | 8 / 3 | |
| 3.0.39 | 8 / 3 | |
| 3.0.38 | 8 / 3 | |
| 3.0.37 | 8 / 3 | |
| 3.0.36 | 8 / 3 | |
| 3.0.35 | 8 / 3 | |
| 3.0.34 | 8 / 3 | |
| 3.0.33 | 8 / 3 | |
| 3.0.32 | 8 / 3 | |
| 3.0.31 | 8 / 3 | |
| 3.0.30 | 8 / 3 | |
| 3.0.29 | 8 / 3 | |
| 3.0.28 | 8 / 3 | |
| 3.0.27 | 8 / 3 | |
| 3.0.26 | 8 / 3 | |
| 3.0.25 | 8 / 3 | |
| 3.0.24 | 8 / 3 | |
| 3.0.23 | 8 / 3 | |
| 3.0.21 | 8 / 3 | |
| 3.0.20 | 8 / 3 | |
| 3.0.19 | 8 / 3 | |
| 3.0.18 | 8 / 3 | |
| 3.0.17 | 8 / 3 | |
| 3.0.16 | 8 / 3 | |
| 3.0.15 | 8 / 3 | |
| 3.0.14 | 8 / 3 | |
| 3.0.13 | 8 / 3 | |
| 3.0.12 | 8 / 4 | |
| 3.0.11 | 8 / 4 | |
| 3.0.10 | 8 / 4 | |
| 3.0.9 | 8 / 4 | |
| 3.0.8 | 8 / 4 | |
| 3.0.7 | 8 / 4 | |
| 3.0.6 | 8 / 4 | |
| 3.0.5 | 8 / 4 | |
| 3.0.4 | 8 / 4 | |
| 3.0.3 | 8 / 4 | |
| 3.0.2 | 8 / 4 | |
| 3.0.1 | 8 / 4 | |
| 3.0.0 | 8 / 4 |
v3.9.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.46
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 (mohammadalfaiyaz_bitgo) than the most recent previously approved version (pranavjain) on 2025-04-25, but mohammadalfaiyaz_bitgo 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.
v3.0.45
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 (pranavjain) than the most recent previously approved version (mohammadalfaiyaz_bitgo) on 2025-04-15, but pranavjain 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.
v3.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.43
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 (mohammadalfaiyaz_bitgo) than the most recent previously approved version (pranavjain) on 2025-04-02, but mohammadalfaiyaz_bitgo 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.
v3.0.42
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 (mohammadalfaiyaz_bitgo) than the most recent previously approved version (pranavjain) on 2025-03-28, but mohammadalfaiyaz_bitgo 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.
v3.0.41
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 (pranavjain) than the most recent previously approved version (alebusse) on 2025-03-20, but pranavjain 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.
v3.0.40
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 (pranavjain) than the most recent previously approved version (alebusse) on 2025-03-18, but pranavjain 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.
v3.0.39
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 (alebusse) than the most recent previously approved version (margueriteblair) on 2025-03-06, but alebusse 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.
v3.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.28
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 (alebusse) than the most recent previously approved version (margueriteblair) on 2025-01-15, but alebusse 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.
v3.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.26
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 (alebusse) than the most recent previously approved version (margueriteblair) on 2025-01-03, but alebusse 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.
v3.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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 (margueriteblair) than the most recent previously approved version (alebusse) on 2024-12-17, but margueriteblair 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.
v3.0.21
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 (margueriteblair) than the most recent previously approved version (alebusse) on 2024-12-12, but margueriteblair 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.
v3.0.20
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 (alebusse) than the most recent previously approved version (margueriteblair) on 2024-12-11, but alebusse 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.
v3.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
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 (margueriteblair) than the most recent previously approved version (pengyuc_bitgo) on 2024-11-19, but margueriteblair 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.
v3.0.15
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 (margueriteblair) than the most recent previously approved version (pengyuc_bitgo) on 2024-11-14, but margueriteblair 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.
v3.0.14
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 (pengyuc_bitgo) than the most recent previously approved version (pranavjain) on 2024-11-08, but pengyuc_bitgo 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.
v3.0.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 (pranavjain) than the most recent previously approved version (alebusse) on 2024-11-07, but pranavjain 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.
v3.0.12
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 (alebusse) than the most recent previously approved version (margueriteblair) on 2024-11-01, but alebusse 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.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
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 (margueriteblair) than the most recent previously approved version (pengyuc_bitgo) on 2024-10-15, but margueriteblair 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.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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 (pengyuc_bitgo) than the most recent previously approved version (alebusse) on 2024-10-04, but pengyuc_bitgo 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.
v3.0.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 (alebusse) than the most recent previously approved version (pranavjain) on 2024-09-24, but alebusse 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.
v3.0.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 (pranavjain) than the most recent previously approved version (zahin-mohammad) on 2024-09-19, but pranavjain 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.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
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 (zahin-mohammad) than the most recent previously approved version (pengyuc_bitgo) on 2024-09-10, but zahin-mohammad 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.
v3.0.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 (pengyuc_bitgo) than the most recent previously approved version (margueriteblair) on 2024-09-03, but pengyuc_bitgo 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.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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 (margueriteblair) than the most recent previously approved version (pengyuc_bitgo) on 2024-08-27, but margueriteblair 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.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.