@bitgo/sdk-coin-sei
BitGo SDK coin library for Sei
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@bitgo/sdk-lib-mpc | AI (phantom-deps): Same-org transitive dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@cosmjs/encoding | AI (phantom-deps): Listed in dependencies; phantom-dep heuristic fires on config-only references, stable false positive. | ai |
Versions (showing 51 of 83)
| Version | Deps | Published |
|---|---|---|
| 3.7.26 | 8 / 3 | |
| 3.7.25 | 8 / 3 | |
| 3.7.23 | 8 / 3 | |
| 3.7.22 | 8 / 3 | |
| 3.7.21 | 8 / 3 | |
| 3.7.20 | 8 / 3 | |
| 3.7.19 | 8 / 3 | |
| 3.7.18 | 8 / 3 | |
| 3.7.17 | 8 / 3 | |
| 3.7.16 | 8 / 3 | |
| 3.7.15 | 8 / 3 | |
| 3.7.14 | 8 / 3 | |
| 3.7.13 | 8 / 3 | |
| 3.7.12 | 8 / 3 | |
| 3.7.11 | 8 / 3 | |
| 3.7.10 | 8 / 3 | |
| 3.7.9 | 8 / 3 | |
| 3.7.8 | 8 / 3 | |
| 3.7.7 | 8 / 3 | |
| 3.7.6 | 8 / 3 | |
| 3.2.3 | 8 / 3 | |
| 3.2.2 | 8 / 3 | |
| 3.2.0 | 8 / 3 | |
| 3.1.11 | 8 / 3 | |
| 3.1.10 | 8 / 3 | |
| 3.1.9 | 8 / 3 | |
| 3.1.8 | 8 / 3 | |
| 3.1.7 | 8 / 3 | |
| 3.1.6 | 8 / 3 | |
| 3.1.4 | 8 / 3 | |
| 3.1.3 | 8 / 3 | |
| 3.1.2 | 8 / 3 | |
| 3.1.1 | 8 / 3 | |
| 3.0.50 | 8 / 3 | |
| 3.0.49 | 8 / 3 | |
| 3.0.48 | 8 / 3 | |
| 3.0.47 | 8 / 3 | |
| 3.0.46 | 8 / 3 | |
| 3.0.45 | 8 / 3 | |
| 3.0.44 | 8 / 3 | |
| 3.0.43 | 8 / 3 | |
| 3.0.42 | 8 / 3 | |
| 3.0.41 | 8 / 3 | |
| 3.0.40 | 8 / 3 | |
| 3.0.39 | 8 / 3 | |
| 3.0.38 | 8 / 3 | |
| 3.0.37 | 8 / 3 | |
| 3.0.36 | 8 / 3 | |
| 3.0.35 | 8 / 3 | |
| 3.0.34 | 8 / 3 | |
| 3.0.33 | 8 / 3 |
v3.7.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.46
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mohammadalfaiyaz_bitgo) than the most recent previously approved version (pranavjain) on 2025-04-25, but mohammadalfaiyaz_bitgo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.45
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pranavjain) than the most recent previously approved version (mohammadalfaiyaz_bitgo) on 2025-04-15, but pranavjain is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.42
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mohammadalfaiyaz_bitgo) than the most recent previously approved version (pranavjain) on 2025-03-28, but mohammadalfaiyaz_bitgo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.40
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pranavjain) than the most recent previously approved version (margueriteblair) on 2025-03-18, but pranavjain is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.39
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alebusse) than the most recent previously approved version (margueriteblair) on 2025-03-06, but alebusse is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.