@bitgo/sdk-coin-xlm
BitGo SDK coin library for Xlm
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-removed | AI (maintainer-change): Mass removal of individual BitGo maintainers consistent with org-wide bot-publisher migration. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): bitgobot addition is part of BitGo org-wide automation rollout, not a takeover. | ai | |
| provenance | publisher-changed | AI (provenance): BitGo org-wide migration to bitgobot publisher; consistent across many approved packages. | ai | |
| phantom-deps | phantom-dep:stellar-sdk | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:bignumber.js | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:@bitgo/sdk-core | AI (phantom-deps): Same-org declared dep; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@bitgo/statics | AI (phantom-deps): Same-org declared dep; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared runtime dep in BitGo monorepo; phantom-dep heuristic fires on indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:superagent | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on indirect usage patterns. | 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): First-party BitGo monorepo package; stable false positive for this package family. | ai |
Versions (showing 33 of 133)
| Version | Deps | Published |
|---|---|---|
| 3.2.16 | 6 / 2 | |
| 3.2.15 | 6 / 2 | |
| 3.2.14 | 6 / 2 | |
| 3.2.13 | 6 / 2 | |
| 3.2.12 | 6 / 2 | |
| 3.2.11 | 6 / 2 | |
| 3.2.10 | 6 / 2 | |
| 3.2.9 | 6 / 2 | |
| 3.2.8 | 6 / 2 | |
| 3.2.7 | 6 / 2 | |
| 3.2.6 | 6 / 2 | |
| 3.2.5 | 6 / 2 | |
| 3.2.4 | 6 / 2 | |
| 3.2.3 | 6 / 2 | |
| 3.2.2 | 6 / 2 | |
| 3.2.1 | 6 / 2 | |
| 3.2.0 | 6 / 2 | |
| 3.1.3 | 6 / 2 | |
| 3.1.2 | 6 / 2 | |
| 3.1.1 | 6 / 2 | |
| 3.1.0 | 6 / 2 | |
| 3.0.21 | 6 / 2 | |
| 3.0.20 | 6 / 2 | |
| 3.0.19 | 6 / 2 | |
| 3.0.18 | 6 / 2 | |
| 3.0.17 | 6 / 2 | |
| 3.0.16 | 6 / 2 | |
| 3.0.15 | 6 / 2 | |
| 3.0.14 | 6 / 2 | |
| 3.0.13 | 6 / 2 | |
| 3.0.12 | 6 / 2 | |
| 3.0.11 | 6 / 2 | |
| 3.0.10 | 6 / 2 |
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.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.
v3.2.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.
v3.2.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.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.