← Home

@bitgo/sdk-coin-rune

BitGo SDK coin library for Thorchain

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
provenance publisher-changed AI (provenance): BitGo migrated publishing to GitHub Actions CI with SLSA attestation; stable pattern for this org. ai
maintainer-change maintainer-added AI (maintainer-change): louib-bitgo is a BitGo-namespaced account; consistent with internal team change, not external takeover. ai
phantom-deps phantom-dep:@cosmjs/encoding AI (phantom-deps): @cosmjs/encoding is a declared runtime dep used in config/type references; stable false positive for this package. ai

Versions (showing 100 of 120)

Version Deps Published
1.9.14 10 / 2
1.9.13 10 / 2
1.9.11 10 / 2
1.9.10 10 / 2
1.9.9 10 / 2
1.9.8 10 / 2
1.9.7 10 / 2
1.9.6 10 / 2
1.9.5 10 / 2
1.9.4 10 / 2
1.9.3 10 / 2
1.9.2 10 / 2
1.9.1 10 / 2
1.9.0 10 / 2
1.8.11 10 / 2
1.8.10 10 / 2
1.8.9 10 / 2
1.8.8 10 / 2
1.8.7 10 / 2
1.8.6 10 / 2
1.8.5 10 / 2
1.8.4 10 / 2
1.8.3 10 / 2
1.8.2 10 / 2
1.8.1 10 / 2
1.8.0 10 / 2
1.7.9 10 / 2
1.7.8 10 / 2
1.7.7 10 / 2
1.7.6 10 / 2
1.7.5 10 / 2
1.7.4 10 / 2
1.7.3 10 / 2
1.7.2 10 / 2
1.7.1 10 / 2
1.7.0 10 / 2
1.6.24 10 / 2
1.6.22 10 / 2
1.6.21 10 / 2
1.6.20 10 / 2
1.6.19 10 / 2
1.6.18 10 / 2
1.6.17 10 / 2
1.6.16 10 / 2
1.6.15 10 / 2
1.6.14 10 / 2
1.6.13 10 / 2
1.6.12 10 / 2
1.6.11 10 / 2
1.6.10 10 / 2
1.6.9 10 / 2
1.6.8 10 / 2
1.6.7 10 / 2
1.6.6 10 / 2
1.6.5 10 / 2
1.6.4 10 / 2
1.6.3 10 / 2
1.6.2 10 / 2
1.6.1 10 / 2
1.6.0 10 / 2
1.5.2 10 / 2
1.5.1 10 / 2
1.5.0 10 / 2
1.4.1 10 / 2
1.4.0 10 / 2
1.3.2 10 / 2
1.3.1 10 / 2
1.3.0 10 / 2
1.2.11 10 / 2
1.2.10 10 / 2
1.2.9 10 / 2
1.2.8 10 / 2
1.2.7 10 / 2
1.2.6 10 / 2
1.2.5 10 / 2
1.2.4 10 / 2
1.2.3 10 / 2
1.2.2 10 / 2
1.2.1 10 / 2
1.2.0 10 / 2
1.1.40 10 / 2
1.1.39 10 / 2
1.1.38 10 / 2
1.1.37 10 / 2
1.1.36 10 / 2
1.1.35 10 / 2
1.1.34 10 / 2
1.1.33 10 / 2
1.1.32 10 / 2
1.1.31 10 / 2
1.1.30 10 / 2
1.1.29 10 / 2
1.1.28 10 / 2
1.1.27 10 / 2
1.1.26 10 / 2
1.1.25 10 / 2
1.1.24 10 / 2
1.1.23 10 / 2
1.1.22 10 / 2
1.1.21 10 / 2
Showing 100 of 120 Next page →

v1.9.14

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.

v1.9.13

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.

v1.9.11

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.

v1.9.10

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.

v1.9.9

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.

v1.9.8

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.

v1.1.34

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.

v1.1.33

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.

v1.1.32

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.

v1.1.31

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.

v1.1.30

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.

v1.1.29

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.

v1.1.28

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.

v1.1.27

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.

v1.1.26

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.

v1.1.25

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.

v1.1.24

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.

v1.1.23

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.

v1.1.22

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.

v1.1.21

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.