@bitgo/sdk-coin-tia
BitGo SDK coin library for Celestia
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): bitgobot is BitGo's automation account with 104 approved packages; consolidation is an org-wide pattern. | ai | |
| source-diff | obfuscated-file:dist/test/unit/keyPair.js | AI (source-diff): Standard tsc output of test file; long lines are base64 tx fixtures, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/StakingActivateBuilder.js | AI (source-diff): Standard tsc output of test file; long lines are base64 tx fixtures, not obfuscation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): BitGo org maintainer rotation; consistent with team changes at a large org. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/transferBuilder.js | AI (source-diff): Standard tsc output of test file; long lines are base64 tx fixtures, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/utils.js | AI (source-diff): Standard tsc output of test file; long lines are base64 tx fixtures, not obfuscation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): BitGo org maintainer rotation; bitgobot is the known CI publishing account. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/StakingDeactivateBuilder.js | AI (source-diff): Standard tsc output of test file; long lines are base64 tx fixtures, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/StakingWithdrawRewardsBuilder.js | AI (source-diff): Standard tsc output of test file; long lines are base64 tx fixtures, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/resources/tia.js | AI (source-diff): Test resource file with base64-encoded transaction test vectors; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/test/unit/tia.js | AI (source-diff): Standard tsc output of test file; long lines are base64 tx fixtures, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transaction.js | AI (source-diff): Standard tsc output of test file; long lines are base64 tx fixtures, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/transactionBuilder.js | AI (source-diff): Standard tsc output of test file; long lines are base64 tx fixtures, not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): New publisher zahin-mohammad is an established BitGo org contributor with 54 approved packages; routine internal handoff. | ai | |
| phantom-deps | phantom-dep:@bitgo/sdk-lib-mpc | AI (phantom-deps): Same-org transitive dep; phantom-dep heuristic is a 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 misfires for this package. | ai |
Versions (showing 33 of 133)
| Version | Deps | Published |
|---|---|---|
| 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.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.