@bitgo/sdk-coin-wemix
BitGo SDK coin library for Wemix
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): BitGo consolidated to bitgobot CI account across their monorepo; 122 approved packages with 0 rejected confirms legitimacy. | ai | |
| source-diff | obfuscated-file:dist/test/resources.js | AI (source-diff): Long lines are hex-encoded transaction fixtures and base64 sourcemaps in compiled TS test output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/send.js | AI (source-diff): Standard TypeScript compiled test file with inline sourcemap; long lines are base64 sourcemap data. | ai | |
| source-diff | obfuscated-file:dist/test/unit/utils.js | AI (source-diff): Standard TypeScript compiled test file with inline sourcemap; long lines are base64 sourcemap data. | ai | |
| source-diff | obfuscated-file:dist/test/unit/wemix.js | AI (source-diff): Standard TypeScript compiled test file with inline sourcemap; long lines are base64 sourcemap data. | ai | |
| provenance | publisher-changed | AI (provenance): BitGo migrated publishing to GitHub Actions CI with SLSA attestation; this is a legitimate pipeline change for the org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): louib-bitgo is a BitGo org account; addition consistent with internal team changes, not a takeover. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/tx | AI (phantom-deps): @ethereumjs/tx is a declared runtime dep used in config/type references; stable false positive for this package. | ai |
Versions (showing 100 of 102)
| Version | Deps | Published |
|---|---|---|
| 1.7.26 | 5 / 2 | |
| 1.7.25 | 5 / 2 | |
| 1.7.23 | 5 / 2 | |
| 1.7.22 | 5 / 2 | |
| 1.7.21 | 5 / 2 | |
| 1.7.20 | 5 / 2 | |
| 1.7.19 | 5 / 2 | |
| 1.7.18 | 5 / 2 | |
| 1.7.17 | 5 / 2 | |
| 1.7.16 | 5 / 2 | |
| 1.7.15 | 5 / 2 | |
| 1.7.14 | 5 / 2 | |
| 1.7.13 | 5 / 2 | |
| 1.7.12 | 5 / 2 | |
| 1.7.11 | 5 / 2 | |
| 1.7.10 | 5 / 2 | |
| 1.7.9 | 5 / 2 | |
| 1.7.8 | 5 / 2 | |
| 1.7.7 | 5 / 2 | |
| 1.7.6 | 5 / 2 | |
| 1.7.5 | 5 / 2 | |
| 1.7.4 | 5 / 2 | |
| 1.7.3 | 5 / 2 | |
| 1.7.2 | 5 / 2 | |
| 1.7.1 | 5 / 2 | |
| 1.7.0 | 5 / 2 | |
| 1.6.9 | 5 / 2 | |
| 1.6.8 | 5 / 2 | |
| 1.6.7 | 5 / 2 | |
| 1.6.6 | 5 / 2 | |
| 1.6.5 | 5 / 2 | |
| 1.6.4 | 5 / 2 | |
| 1.6.3 | 5 / 2 | |
| 1.6.2 | 5 / 2 | |
| 1.6.1 | 5 / 2 | |
| 1.6.0 | 5 / 2 | |
| 1.5.24 | 5 / 2 | |
| 1.5.22 | 5 / 2 | |
| 1.5.21 | 5 / 2 | |
| 1.5.20 | 5 / 2 | |
| 1.5.19 | 5 / 2 | |
| 1.5.18 | 5 / 2 | |
| 1.5.17 | 5 / 2 | |
| 1.5.16 | 5 / 2 | |
| 1.5.15 | 5 / 2 | |
| 1.5.14 | 5 / 2 | |
| 1.5.13 | 5 / 2 | |
| 1.5.12 | 5 / 2 | |
| 1.5.11 | 5 / 2 | |
| 1.5.10 | 5 / 2 | |
| 1.5.9 | 5 / 2 | |
| 1.5.8 | 5 / 2 | |
| 1.5.7 | 5 / 2 | |
| 1.5.6 | 5 / 2 | |
| 1.5.5 | 5 / 2 | |
| 1.5.4 | 5 / 2 | |
| 1.5.3 | 5 / 2 | |
| 1.5.2 | 5 / 2 | |
| 1.5.1 | 5 / 2 | |
| 1.5.0 | 5 / 2 | |
| 1.4.4 | 5 / 2 | |
| 1.4.3 | 5 / 2 | |
| 1.4.2 | 5 / 2 | |
| 1.4.1 | 5 / 2 | |
| 1.4.0 | 5 / 2 | |
| 1.3.15 | 5 / 2 | |
| 1.3.14 | 5 / 2 | |
| 1.3.13 | 5 / 2 | |
| 1.3.12 | 5 / 2 | |
| 1.3.11 | 5 / 2 | |
| 1.3.10 | 5 / 2 | |
| 1.3.9 | 5 / 2 | |
| 1.3.8 | 5 / 2 | |
| 1.3.7 | 5 / 2 | |
| 1.3.6 | 5 / 2 | |
| 1.3.5 | 5 / 2 | |
| 1.3.4 | 5 / 2 | |
| 1.3.3 | 5 / 2 | |
| 1.3.2 | 5 / 2 | |
| 1.3.1 | 5 / 2 | |
| 1.3.0 | 5 / 2 | |
| 1.2.7 | 5 / 2 | |
| 1.2.6 | 5 / 2 | |
| 1.2.5 | 5 / 2 | |
| 1.2.4 | 5 / 2 | |
| 1.2.3 | 5 / 2 | |
| 1.2.2 | 5 / 2 | |
| 1.2.1 | 5 / 2 | |
| 1.2.0 | 5 / 2 | |
| 1.1.12 | 4 / 2 | |
| 1.1.11 | 4 / 2 | |
| 1.1.10 | 4 / 2 | |
| 1.1.9 | 4 / 2 | |
| 1.1.8 | 4 / 2 | |
| 1.1.7 | 4 / 2 | |
| 1.1.6 | 4 / 2 | |
| 1.1.5 | 4 / 2 | |
| 1.1.4 | 4 / 2 | |
| 1.1.3 | 4 / 2 | |
| 1.1.2 | 4 / 2 |
v1.7.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.