@bitgo/sdk-coin-hbar
BitGo SDK coin library for Hbar
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@bitgo/sdk-coin-algo | AI (phantom-deps): Same org scope; stable false positive for this BitGo coin module. | ai | |
| phantom-deps | phantom-dep:@bitgo/statics | AI (phantom-deps): Same org scope; stable false positive for this BitGo coin module. | ai | |
| phantom-deps | phantom-dep:@hashgraph/sdk | AI (phantom-deps): Core Hedera SDK dep; stable false positive for this coin module. | ai | |
| phantom-deps | phantom-dep:@bitgo/sdk-core | AI (phantom-deps): Same org scope; stable false positive for this BitGo coin module. | ai | |
| phantom-deps | phantom-dep:@hashgraph/proto | AI (phantom-deps): Hedera proto dep; stable false positive for this coin module. | ai | |
| phantom-deps | phantom-dep:@stablelib/sha384 | AI (phantom-deps): Stable false positive; crypto dep used via config/indirect imports. | ai | |
| phantom-deps | phantom-dep:long | AI (phantom-deps): All phantom deps are legitimate runtime dependencies referenced in config/type files for this Hedera SDK coin module. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Stable false positive for this package; lodash is a real transitive/config-referenced dep. | ai | |
| phantom-deps | phantom-dep:tweetnacl | AI (phantom-deps): Stable false positive; tweetnacl used via config/indirect imports in this coin module. | ai | |
| phantom-deps | phantom-dep:stellar-sdk | AI (phantom-deps): Stable false positive; stellar-sdk referenced in config files for this coin module. | ai | |
| phantom-deps | phantom-dep:bignumber.js | AI (phantom-deps): Stable false positive; bignumber.js is a real dep used via config/indirect imports. | ai | |
| source-diff | obfuscated-file:dist/src/lib/accountUpdateBuilder.js | AI (source-diff): Standard tsc CommonJS output with inline sourcemaps; long lines are base64 sourcemap data, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/accountUpdateBuilder.js | AI (source-diff): Standard tsc test output; long lines from inline sourcemaps. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual BitGo employee accounts in favor of bot account is an org-level policy change, not a takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): bitgobot is BitGo's established publishing bot with 117 approved packages. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): BitGo consolidating to bitgobot automation account; 117 approved packages, consistent org-wide pattern. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/walletInitialization.js | AI (source-diff): Compiled TypeScript test file with inline source map; benign for this package. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/tokenTransferBuilder.js | AI (source-diff): Compiled TypeScript test file with inline source map; benign for this package. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transaction.js | AI (source-diff): Compiled TypeScript test file with inline source map; benign for this package. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/transferBuilder.js | AI (source-diff): Compiled TypeScript test file with inline source map; benign for this package. | ai | |
| source-diff | obfuscated-file:dist/test/unit/utils.js | AI (source-diff): Compiled TypeScript test file with inline source map; benign for this package. | ai | |
| source-diff | obfuscated-file:dist/test/fixtures/hbar.js | AI (source-diff): Long lines are hex-encoded transaction test fixtures, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/test/resources/hbar.js | AI (source-diff): Compiled TypeScript test resource file with inline source maps; benign for this package. | ai | |
| source-diff | obfuscated-file:dist/test/unit/hbar.js | AI (source-diff): Compiled TypeScript test file with inline source map; long lines are base64 source maps. | ai | |
| source-diff | obfuscated-file:dist/test/unit/hbarToken.js | AI (source-diff): Compiled TypeScript test file with inline source map; benign for this package. | ai | |
| source-diff | obfuscated-file:dist/test/unit/keyPair.js | AI (source-diff): Compiled TypeScript test file with inline source map; benign for this package. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/tokenAssociateBuilder.js | AI (source-diff): Compiled TypeScript test file with inline source map; benign for this package. | ai | |
| provenance | publisher-changed | AI (provenance): zahin-mohammad is an established BitGo publisher (63 approved, 0 rejected); transition from mohammadalfaiyaz_bitgo appears to be an internal team change. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/coinTransferBuilder.js | AI (source-diff): TypeScript-compiled test file with standard TS helper boilerplate; not obfuscated. | ai | |
| source-diff | encoded-string-file:dist/test/unit/hbar.js | AI (source-diff): Long hex strings are Hedera serialized transaction test fixtures, not malicious payloads. | ai | |
| phantom-deps | phantom-dep:protobufjs | AI (phantom-deps): protobufjs is explicitly declared as a direct dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 53 of 153)
| Version | Deps | Published |
|---|---|---|
| 2.0.63 | 12 / 2 | |
| 2.0.62 | 12 / 2 | |
| 2.0.61 | 12 / 2 | |
| 2.0.60 | 12 / 2 | |
| 2.0.59 | 12 / 2 | |
| 2.0.58 | 12 / 2 | |
| 2.0.57 | 12 / 2 | |
| 2.0.56 | 12 / 2 | |
| 2.0.55 | 12 / 2 | |
| 2.0.54 | 12 / 2 | |
| 2.0.52 | 12 / 2 | |
| 2.0.51 | 12 / 2 | |
| 2.0.50 | 12 / 2 | |
| 2.0.49 | 12 / 2 | |
| 2.0.48 | 12 / 2 | |
| 2.0.47 | 12 / 2 | |
| 2.0.46 | 12 / 2 | |
| 2.0.45 | 12 / 2 | |
| 2.0.44 | 12 / 2 | |
| 2.0.43 | 12 / 2 | |
| 2.0.42 | 12 / 2 | |
| 2.0.41 | 12 / 2 | |
| 2.0.40 | 12 / 2 | |
| 2.0.39 | 12 / 2 | |
| 2.0.38 | 12 / 2 | |
| 2.0.37 | 12 / 2 | |
| 2.0.36 | 12 / 2 | |
| 2.0.35 | 12 / 2 | |
| 2.0.34 | 12 / 2 | |
| 2.0.33 | 12 / 2 | |
| 2.0.32 | 12 / 2 | |
| 2.0.31 | 12 / 2 | |
| 2.0.30 | 12 / 2 | |
| 2.0.29 | 12 / 2 | |
| 2.0.28 | 12 / 2 | |
| 2.0.27 | 12 / 2 | |
| 2.0.26 | 12 / 2 | |
| 2.0.25 | 12 / 2 | |
| 2.0.24 | 12 / 2 | |
| 2.0.23 | 12 / 2 | |
| 2.0.22 | 12 / 2 | |
| 2.0.21 | 12 / 2 | |
| 2.0.20 | 12 / 2 | |
| 2.0.19 | 12 / 2 | |
| 2.0.18 | 12 / 2 | |
| 2.0.17 | 12 / 2 | |
| 2.0.16 | 12 / 2 | |
| 2.0.15 | 12 / 2 | |
| 2.0.14 | 12 / 2 | |
| 2.0.13 | 12 / 2 | |
| 2.0.12 | 12 / 2 | |
| 2.0.11 | 12 / 2 | |
| 2.0.10 | 12 / 2 |
v2.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.