← Home

@bitgo/sdk-coin-btc

npm Repository Homepage

BitGo SDK coin library for Bitcoin

100
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

louib-bitgobitgobot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/src/inscriptionBuilder.js AI (source-diff): TypeScript tsc-compiled output; long lines are from bundled type helpers, not obfuscation. Normal for this package's build process. ai
provenance publisher-changed AI (provenance): New publisher is an established BitGo org member with 63 approved packages; consistent with internal maintainer rotation. ai
phantom-deps phantom-dep:@bitgo/utxo-lib AI (phantom-deps): Same-org monorepo package; stable false positive. ai
phantom-deps phantom-dep:@bitgo/sdk-core AI (phantom-deps): Same-org monorepo package; declared for type re-export, not a direct import concern. ai
phantom-deps phantom-dep:@bitgo/utxo-ord AI (phantom-deps): Same-org monorepo package; stable false positive. ai
phantom-deps phantom-dep:@bitgo/abstract-utxo AI (phantom-deps): Same-org monorepo package; stable false positive. 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/abstract-utxo AI (dependencies): Internal BitGo monorepo dependency; expected and stable for this package. ai
dependencies unvetted-dep:@bitgo/sdk-core AI (dependencies): Internal BitGo monorepo dependency; expected and stable for this package. ai

Versions (showing 100 of 155)

Version Deps Published
2.13.27 2 / 0
2.13.26 2 / 0
2.13.25 2 / 0
2.13.23 2 / 0
2.13.22 2 / 0
2.13.21 2 / 0
2.13.20 2 / 0
2.13.19 2 / 0
2.13.18 2 / 0
2.13.17 2 / 0
2.13.16 2 / 0
2.13.15 2 / 0
2.13.14 2 / 0
2.13.13 2 / 0
2.13.12 2 / 0
2.13.11 2 / 0
2.13.10 2 / 0
2.13.9 2 / 0
2.13.8 2 / 0
2.13.7 2 / 0
2.13.6 2 / 0
2.13.5 2 / 0
2.13.4 2 / 0
2.13.3 2 / 0
2.13.2 2 / 0
2.13.1 2 / 0
2.13.0 2 / 0
2.12.9 2 / 0
2.12.8 2 / 0
2.12.7 2 / 0
2.12.6 2 / 0
2.12.5 2 / 0
2.12.4 2 / 0
2.12.3 2 / 0
2.12.2 2 / 0
2.12.1 2 / 0
2.12.0 2 / 0
2.11.10 2 / 0
2.11.9 2 / 0
2.11.7 2 / 0
2.11.6 2 / 0
2.11.5 2 / 0
2.11.4 2 / 0
2.11.3 2 / 0
2.11.2 2 / 0
2.11.1 2 / 0
2.11.0 2 / 0
2.10.6 2 / 0
2.10.5 2 / 0
2.10.4 2 / 0
2.10.3 2 / 0
2.10.2 2 / 0
2.10.1 2 / 0
2.10.0 2 / 0
2.9.6 4 / 2
2.9.5 4 / 2
2.9.4 4 / 2
2.9.3 4 / 2
2.9.2 4 / 2
2.9.1 4 / 2
2.9.0 4 / 2
2.8.0 4 / 2
2.7.4 4 / 2
2.7.3 4 / 2
2.7.2 4 / 2
2.7.1 4 / 2
2.7.0 4 / 2
2.6.15 4 / 2
2.6.14 4 / 2
2.6.13 4 / 2
2.6.12 4 / 2
2.6.11 4 / 2
2.6.10 4 / 2
2.6.9 4 / 2
2.6.8 4 / 2
2.6.7 4 / 2
2.6.6 4 / 2
2.6.5 4 / 2
2.6.4 4 / 2
2.6.3 4 / 2
2.6.2 4 / 2
2.6.1 4 / 2
2.6.0 4 / 2
2.5.0 4 / 2
2.4.32 4 / 2
2.4.31 4 / 2
2.4.30 4 / 2
2.4.29 4 / 2
2.4.28 4 / 2
2.4.27 4 / 2
2.4.26 4 / 2
2.4.25 4 / 2
2.4.24 4 / 2
2.4.23 4 / 2
2.4.22 4 / 2
2.4.21 4 / 2
2.4.20 4 / 2
2.4.19 4 / 2
2.4.18 4 / 2
2.4.17 4 / 2
Showing 100 of 155 Next page →

v2.13.27

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.13.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.13.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.13.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.13.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.13.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.13.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.4.27

1 finding
INFO No provenance attestation provenance

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

v2.4.26

1 finding
INFO No provenance attestation provenance

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

v2.4.25

1 finding
INFO No provenance attestation provenance

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

v2.4.24

1 finding
INFO No provenance attestation provenance

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

v2.4.23

1 finding
INFO No provenance attestation provenance

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

v2.4.22

1 finding
INFO No provenance attestation provenance

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

v2.4.21

1 finding
INFO No provenance attestation provenance

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

v2.4.20

1 finding
INFO No provenance attestation provenance

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

v2.4.19

1 finding
INFO No provenance attestation provenance

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

v2.4.18

1 finding
INFO No provenance attestation provenance

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

v2.4.17

1 finding
INFO No provenance attestation provenance

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