@bitgo/sdk-coin-islm
BitGo SDK coin library for Islm
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 |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by newly included compiled test directory under dist/test/. | ai | |
| source-diff | obfuscated-file:dist/test/unit/utils.js | AI (source-diff): Compiled TypeScript unit test; long lines are standard TS boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/transferBuilder.js | AI (source-diff): Compiled TypeScript unit test; long lines are standard TS boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/transactionBuilder.js | AI (source-diff): Compiled TypeScript unit test; long lines are standard TS boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transaction.js | AI (source-diff): Compiled TypeScript unit test; long lines are standard TS boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/StakingWithdrawRewardsBuilder.js | AI (source-diff): Compiled TypeScript unit test; long lines are standard TS boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/StakingDeactivateBuilder.js | AI (source-diff): Compiled TypeScript unit test; long lines are standard TS boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/StakingActivateBuilder.js | AI (source-diff): Compiled TypeScript unit test; long lines are standard TS boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/keyPair.js | AI (source-diff): Compiled TypeScript unit test; long lines are standard TS boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/islm.js | AI (source-diff): Compiled TypeScript unit test; long lines are standard TS boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/resources/islm.js | AI (source-diff): Compiled TypeScript test fixture with hardcoded test vectors; long lines from base64 tx data, not obfuscation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Bulk removal of individual BitGo maintainers consistent with org-wide bot-publisher migration. | ai | |
| provenance | publisher-changed | AI (provenance): BitGo org-wide migration to bitgobot publisher; stable pattern across hundreds of approved packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Addition of bitgobot reflects org-level automation transition, not a takeover. | ai | |
| phantom-deps | phantom-dep:@bitgo/abstract-cosmos | AI (phantom-deps): Declared dependency; same org scope. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@cosmjs/encoding | AI (phantom-deps): Declared dependency; referenced in config files. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@bitgo/sdk-core | AI (phantom-deps): Declared dependency; same org scope. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@bitgo/statics | AI (phantom-deps): Declared dependency; same org scope. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@cosmjs/amino | AI (phantom-deps): Declared dependency; referenced in config files. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:cosmjs-types | AI (phantom-deps): Declared dependency; referenced in config files. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:bignumber.js | AI (phantom-deps): Declared dependency; referenced in config files. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:keccak | AI (phantom-deps): Declared dependency; referenced in config files. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:ethers | AI (phantom-deps): Declared dependency; referenced in config files. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@cosmjs/proto-signing | AI (phantom-deps): Declared dependency; referenced in config files. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@cosmjs/stargate | AI (phantom-deps): Declared dependency; referenced in config files. Stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): BitGo monorepo packages consistently lack Sigstore provenance; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@bitgo/sdk-core | AI (dependencies): Internal BitGo monorepo dependency; expected and stable for this package family. | ai | |
| dependencies | unvetted-dep:@bitgo/abstract-cosmos | AI (dependencies): Internal BitGo monorepo dependency; expected and stable for this package family. | ai |
Versions (showing 54 of 154)
| Version | Deps | Published |
|---|---|---|
| 2.1.14 | 12 / 3 | |
| 2.1.13 | 12 / 3 | |
| 2.1.12 | 12 / 3 | |
| 2.1.11 | 12 / 3 | |
| 2.1.10 | 12 / 3 | |
| 2.1.9 | 12 / 3 | |
| 2.1.8 | 12 / 3 | |
| 2.1.7 | 12 / 3 | |
| 2.1.6 | 12 / 3 | |
| 2.1.5 | 12 / 3 | |
| 2.1.4 | 12 / 3 | |
| 2.1.2 | 12 / 3 | |
| 2.1.1 | 12 / 3 | |
| 2.1.0 | 12 / 3 | |
| 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.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.