@bitgo/sdk-coin-injective MIT 33 versions

@bitgo/sdk-coin-injective

npm Repository Homepage

BitGo SDK coin library for Injective

33

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

louib-bitgobitgobot

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): BitGo org-wide migration to GitHub Actions CI publishing with SLSA provenance; new maintainers fit BitGo naming pattern.	ai	2026/05/30
source-diff	obfuscated-file:dist/test/unit/transactionBuilder/StakingWithdrawRewardsBuilder.js	AI (source-diff): Compiled TypeScript unit test; long lines are standard test patterns.	ai	2026/05/30
source-diff	obfuscated-file:dist/test/unit/transaction.js	AI (source-diff): Compiled TypeScript unit test; long lines are standard test patterns.	ai	2026/05/30
source-diff	obfuscated-file:dist/test/unit/transactionBuilder/transactionBuilder.js	AI (source-diff): Compiled TypeScript unit test; long lines are standard test patterns.	ai	2026/05/30
source-diff	obfuscated-file:dist/test/unit/transactionBuilder/transferBuilder.js	AI (source-diff): Compiled TypeScript unit test; long lines are standard test patterns.	ai	2026/05/30
source-diff	obfuscated-file:dist/test/unit/utils.js	AI (source-diff): Compiled TypeScript unit test; long lines are standard test patterns.	ai	2026/05/30
source-diff	obfuscated-file:dist/test/resources/injective.js	AI (source-diff): Compiled TypeScript test fixture with long base64 transaction vectors; not obfuscated malware.	ai	2026/05/30
source-diff	obfuscated-file:dist/test/unit/injective.js	AI (source-diff): Compiled TypeScript unit test file; long lines are standard mocha test patterns.	ai	2026/05/30
source-diff	obfuscated-file:dist/test/unit/keyPair.js	AI (source-diff): Compiled TypeScript unit test; long lines are standard test patterns.	ai	2026/05/30
source-diff	obfuscated-file:dist/test/unit/transactionBuilder/StakingActivateBuilder.js	AI (source-diff): Compiled TypeScript unit test; long lines are standard test patterns.	ai	2026/05/30
source-diff	obfuscated-file:dist/test/unit/transactionBuilder/StakingDeactivateBuilder.js	AI (source-diff): Compiled TypeScript unit test; long lines are standard test patterns.	ai	2026/05/30
provenance	publisher-changed	AI (provenance): BitGo internal account rotation; bitgobot is a well-established org publisher with 290 approved packages.	ai	2026/05/18
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers are BitGo org accounts; consistent with internal team restructuring.	ai	2026/05/18
maintainer-change	maintainer-removed	AI (maintainer-change): Removed maintainers are prior BitGo org accounts; routine org-level maintainer consolidation.	ai	2026/05/18
phantom-deps	phantom-dep:@cosmjs/encoding	AI (phantom-deps): Declared in dependencies and used transitively; stable false positive for this package.	ai	2026/05/17
phantom-deps	phantom-dep:@bitgo/sdk-lib-mpc	AI (phantom-deps): Same-org transitive dep; phantom-dep heuristic false positive for this package.	ai	2026/05/17

Versions (showing 33 of 133)

Version	Deps	Published
3.0.33	8 / 3	2025-02-05
3.0.32	8 / 3	2025-01-28
3.0.31	8 / 3	2025-01-23
3.0.30	8 / 3	2025-01-23
3.0.29	8 / 3	2025-01-20
3.0.28	8 / 3	2025-01-15
3.0.27	8 / 3	2025-01-09
3.0.26	8 / 3	2025-01-03
3.0.25	8 / 3	2024-12-24
3.0.24	8 / 3	2024-12-19
3.0.23	8 / 3	2024-12-17
3.0.21	8 / 3	2024-12-12
3.0.20	8 / 3	2024-12-11
3.0.19	8 / 3	2024-12-03
3.0.18	8 / 3	2024-11-26
3.0.17	8 / 3	2024-11-21
3.0.16	8 / 3	2024-11-19
3.0.15	8 / 3	2024-11-14
3.0.14	8 / 3	2024-11-08
3.0.13	8 / 3	2024-11-07
3.0.12	8 / 4	2024-11-01
3.0.11	8 / 4	2024-10-22
3.0.10	8 / 4	2024-10-15
3.0.9	8 / 4	2024-10-08
3.0.8	8 / 4	2024-10-04
3.0.7	8 / 4	2024-09-24
3.0.6	8 / 4	2024-09-19
3.0.5	8 / 4	2024-09-16
3.0.4	8 / 4	2024-09-10
3.0.3	8 / 4	2024-09-03
3.0.2	8 / 4	2024-08-29
3.0.1	8 / 4	2024-08-27
3.0.0	8 / 4	2024-08-20

v3.0.33

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.32

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.