@bitgo/sdk-coin-polyx
BitGo SDK coin library for POLYX (Polymesh) coin
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 | obfuscated-file:dist/src/resources/mainnet.js | AI (source-diff): Long hex string is Substrate chain metadata (SCALE-encoded), not obfuscation; stable pattern for this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by addition of 1.8MB mainnet/testnet Substrate metadata resource files, not injected payloads. | ai | |
| source-diff | obfuscated-file:dist/src/lib/registerDidWithCDDBuilder.js | AI (source-diff): Readable TypeScript-compiled class; long-line flag is a false positive from bundled imports or type annotations. | ai | |
| source-diff | obfuscated-file:dist/src/resources/testnet.js | AI (source-diff): Same as mainnet.js — Substrate chain metadata blob, expected for Polymesh SDK coin module. | ai | |
| provenance | no-provenance | AI (provenance): BitGo SDK packages consistently lack Sigstore provenance; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@bitgo/sdk-core | AI (dependencies): Core BitGo SDK dep; expected internal dependency for all @bitgo/sdk-coin-* packages. | ai | |
| dependencies | unvetted-dep:@substrate/txwrapper-polkadot | AI (dependencies): Standard Substrate ecosystem library for Polkadot transactions; well-known upstream dep. | ai | |
| dependencies | unvetted-dep:@substrate/txwrapper-core | AI (dependencies): Standard Substrate ecosystem library for transaction wrapping; well-known upstream dep. | ai | |
| dependencies | unvetted-dep:@bitgo/abstract-substrate | AI (dependencies): Internal BitGo Substrate abstraction; expected for Polkadot-based coin modules. | ai | |
| dependencies | unvetted-dep:@bitgo/sdk-lib-mpc | AI (dependencies): Internal BitGo MPC library; expected for BitGo coin SDK packages. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.15.1 | 10 / 2 | |
| 1.15.0 | 10 / 2 | |
| 1.14.9 | 10 / 2 | |
| 1.14.8 | 10 / 2 | |
| 1.14.7 | 10 / 2 | |
| 1.14.6 | 10 / 2 | |
| 1.14.5 | 10 / 2 | |
| 1.9.3 | 10 / 2 | |
| 1.1.2 | 8 / 2 | |
| 1.1.1 | 8 / 2 | |
| 1.1.0 | 7 / 2 | |
| 1.0.4 | 4 / 2 | |
| 1.0.3 | 4 / 2 |
v1.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.14.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.14.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.14.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.14.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.14.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
5 findingsThis version was published by a different npm account than previous versions on 2025-05-28. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.