← Home

@bitgo/sdk-coin-coredao

npm Repository Homepage

BitGo SDK coin library for Coredao

48
Versions
MIT
License
No
Install Scripts
Attested
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

louib-bitgobitgobot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@ethereumjs/tx AI (phantom-deps): @ethereumjs/tx is a declared runtime dep in package.json; phantom-dep false positive for this package. ai

Versions (showing 48 of 48)

Version Deps Published
2.8.26 6 / 2
2.8.25 6 / 2
2.8.23 6 / 2
2.8.22 6 / 2
2.8.21 6 / 2
2.8.20 6 / 2
2.8.19 6 / 2
2.8.18 6 / 2
2.8.17 6 / 2
2.8.16 6 / 2
2.8.15 6 / 2
2.8.14 6 / 2
2.8.13 6 / 2
2.8.12 6 / 2
2.8.11 6 / 2
2.8.10 6 / 2
2.8.9 6 / 2
2.8.8 6 / 2
2.8.7 6 / 2
2.8.6 6 / 2
2.5.3 6 / 2
2.5.2 6 / 2
2.5.0 6 / 2
2.4.5 6 / 2
2.4.4 6 / 2
2.4.3 6 / 2
2.3.6 6 / 2
2.3.5 6 / 2
2.3.1 6 / 2
2.3.0 6 / 2
2.2.3 6 / 2
2.2.2 6 / 2
2.2.1 6 / 2
2.2.0 6 / 2
2.1.3 6 / 2
2.1.2 6 / 2
2.1.1 6 / 2
2.1.0 6 / 2
2.0.9 6 / 2
2.0.8 6 / 2
2.0.7 6 / 2
2.0.6 6 / 2
2.0.5 6 / 2
2.0.4 6 / 2
2.0.3 6 / 2
2.0.2 6 / 2
2.0.1 6 / 2
2.0.0 6 / 2

v2.8.26

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.8.25

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.8.23

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.8.22

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.8.21

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.8.20

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mohammadalfaiyaz_bitgo → pranavjain (on 2025-04-15, known maintainer) provenance

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.

v2.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.7

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: pranavjain → mohammadalfaiyaz_bitgo (on 2025-03-28, known maintainer) provenance

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.

v2.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.5

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: alebusse → pranavjain (on 2025-03-18, known maintainer) provenance

This version was published by a different npm account (pranavjain) than the most recent previously approved version (alebusse) 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.

v2.0.4

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: margueriteblair → alebusse (on 2025-03-06, known maintainer) provenance

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.

v2.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.