@bitgo/abstract-substrate
BitGo SDK coin library for Substrate base implementation
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 publishing to bitgobot across their entire SDK; not a hostile takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): bitgobot is BitGo's publishing bot; addition is expected across all BitGo SDK packages. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual maintainers in favor of bitgobot is an org-wide BitGo policy change. | ai | |
| provenance | publisher-changed | AI (provenance): zahin-mohammad is an established BitGo org publisher with 63 approved packages; transition appears legitimate. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established BitGo SDK module; sparse README/no keywords is a style choice, not a spam indicator. | ai |
Versions (showing 100 of 106)
| Version | Deps | Published |
|---|---|---|
| 2.0.4 | 17 / 0 | |
| 2.0.3 | 17 / 0 | |
| 2.0.1 | 17 / 0 | |
| 2.0.0 | 17 / 0 | |
| 1.17.1 | 17 / 0 | |
| 1.17.0 | 17 / 0 | |
| 1.16.7 | 17 / 0 | |
| 1.16.6 | 17 / 0 | |
| 1.16.5 | 17 / 0 | |
| 1.16.4 | 17 / 0 | |
| 1.16.3 | 17 / 0 | |
| 1.16.2 | 17 / 0 | |
| 1.16.1 | 17 / 0 | |
| 1.16.0 | 17 / 0 | |
| 1.15.1 | 17 / 0 | |
| 1.15.0 | 17 / 0 | |
| 1.14.9 | 17 / 0 | |
| 1.14.8 | 17 / 0 | |
| 1.14.7 | 17 / 0 | |
| 1.14.6 | 17 / 0 | |
| 1.14.5 | 17 / 0 | |
| 1.14.4 | 17 / 0 | |
| 1.14.3 | 17 / 0 | |
| 1.14.2 | 17 / 0 | |
| 1.14.1 | 17 / 0 | |
| 1.14.0 | 17 / 0 | |
| 1.13.9 | 17 / 0 | |
| 1.13.8 | 17 / 0 | |
| 1.13.7 | 17 / 0 | |
| 1.13.6 | 17 / 0 | |
| 1.13.5 | 17 / 0 | |
| 1.13.4 | 17 / 0 | |
| 1.13.3 | 17 / 0 | |
| 1.13.2 | 17 / 0 | |
| 1.13.1 | 17 / 0 | |
| 1.13.0 | 17 / 0 | |
| 1.12.4 | 17 / 0 | |
| 1.12.2 | 17 / 0 | |
| 1.12.1 | 17 / 0 | |
| 1.12.0 | 17 / 0 | |
| 1.11.19 | 17 / 0 | |
| 1.11.18 | 17 / 0 | |
| 1.11.17 | 17 / 0 | |
| 1.11.16 | 17 / 0 | |
| 1.11.15 | 17 / 0 | |
| 1.11.14 | 17 / 0 | |
| 1.11.13 | 17 / 0 | |
| 1.11.12 | 17 / 0 | |
| 1.11.11 | 17 / 0 | |
| 1.11.10 | 17 / 0 | |
| 1.11.9 | 17 / 0 | |
| 1.11.8 | 17 / 0 | |
| 1.11.7 | 17 / 0 | |
| 1.11.6 | 17 / 0 | |
| 1.11.5 | 17 / 0 | |
| 1.11.4 | 17 / 0 | |
| 1.11.3 | 17 / 0 | |
| 1.11.2 | 17 / 0 | |
| 1.11.1 | 17 / 0 | |
| 1.11.0 | 17 / 0 | |
| 1.10.4 | 17 / 0 | |
| 1.10.3 | 17 / 0 | |
| 1.10.2 | 17 / 0 | |
| 1.10.1 | 17 / 0 | |
| 1.10.0 | 17 / 0 | |
| 1.9.2 | 17 / 0 | |
| 1.9.1 | 17 / 0 | |
| 1.9.0 | 17 / 0 | |
| 1.8.10 | 17 / 0 | |
| 1.8.9 | 17 / 0 | |
| 1.8.8 | 17 / 0 | |
| 1.8.7 | 17 / 0 | |
| 1.8.6 | 17 / 0 | |
| 1.8.5 | 17 / 0 | |
| 1.8.4 | 17 / 0 | |
| 1.8.3 | 17 / 0 | |
| 1.8.2 | 17 / 0 | |
| 1.8.1 | 17 / 0 | |
| 1.8.0 | 17 / 0 | |
| 1.7.1 | 17 / 0 | |
| 1.7.0 | 17 / 0 | |
| 1.6.0 | 17 / 0 | |
| 1.5.2 | 17 / 0 | |
| 1.5.1 | 17 / 0 | |
| 1.5.0 | 17 / 0 | |
| 1.4.9 | 17 / 0 | |
| 1.4.8 | 17 / 0 | |
| 1.4.7 | 17 / 0 | |
| 1.4.6 | 17 / 0 | |
| 1.4.5 | 17 / 0 | |
| 1.4.4 | 17 / 0 | |
| 1.4.3 | 17 / 0 | |
| 1.4.2 | 17 / 0 | |
| 1.4.1 | 17 / 0 | |
| 1.4.0 | 17 / 0 | |
| 1.3.0 | 15 / 0 | |
| 1.2.0 | 15 / 0 | |
| 1.1.6 | 15 / 0 | |
| 1.1.5 | 15 / 0 | |
| 1.1.4 | 15 / 0 |
v2.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
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.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.