@bitgo/utxo-ord
Utilities for building ordinals with BitGo utxo-lib
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): BitGo monorepo packages consistently publish without Sigstore provenance; stable pattern across all versions. | ai |
Versions (showing 100 of 131)
| Version | Deps | Published |
|---|---|---|
| 1.32.4 | 1 / 1 | |
| 1.32.3 | 1 / 1 | |
| 1.32.2 | 1 / 1 | |
| 1.32.1 | 1 / 1 | |
| 1.32.0 | 1 / 1 | |
| 1.31.0 | 1 / 1 | |
| 1.30.1 | 1 / 1 | |
| 1.30.0 | 1 / 1 | |
| 1.29.1 | 1 / 1 | |
| 1.29.0 | 1 / 1 | |
| 1.27.0 | 1 / 1 | |
| 1.26.0 | 1 / 1 | |
| 1.25.0 | 1 / 1 | |
| 1.24.1 | 3 / 0 | |
| 1.22.22 | 3 / 0 | |
| 1.22.21 | 3 / 0 | |
| 1.22.20 | 3 / 0 | |
| 1.22.19 | 3 / 0 | |
| 1.22.18 | 3 / 0 | |
| 1.22.17 | 3 / 0 | |
| 1.22.16 | 3 / 0 | |
| 1.22.15 | 3 / 0 | |
| 1.22.14 | 3 / 0 | |
| 1.22.13 | 3 / 0 | |
| 1.22.12 | 3 / 0 | |
| 1.22.11 | 3 / 0 | |
| 1.22.10 | 3 / 0 | |
| 1.22.9 | 3 / 0 | |
| 1.22.8 | 3 / 0 | |
| 1.22.7 | 3 / 0 | |
| 1.22.6 | 3 / 0 | |
| 1.22.5 | 3 / 0 | |
| 1.22.4 | 3 / 0 | |
| 1.22.3 | 3 / 0 | |
| 1.22.2 | 3 / 0 | |
| 1.22.1 | 3 / 0 | |
| 1.22.0 | 3 / 0 | |
| 1.21.4 | 3 / 0 | |
| 1.21.3 | 3 / 0 | |
| 1.21.2 | 3 / 0 | |
| 1.21.1 | 3 / 0 | |
| 1.21.0 | 3 / 0 | |
| 1.20.104 | 3 / 0 | |
| 1.20.103 | 3 / 0 | |
| 1.20.102 | 3 / 0 | |
| 1.20.101 | 3 / 0 | |
| 1.20.100 | 3 / 0 | |
| 1.20.99 | 3 / 0 | |
| 1.20.98 | 3 / 0 | |
| 1.20.97 | 3 / 0 | |
| 1.20.96 | 3 / 0 | |
| 1.20.95 | 3 / 0 | |
| 1.20.94 | 3 / 0 | |
| 1.20.93 | 3 / 0 | |
| 1.20.92 | 3 / 0 | |
| 1.20.91 | 3 / 0 | |
| 1.20.90 | 3 / 0 | |
| 1.20.89 | 3 / 0 | |
| 1.20.88 | 3 / 0 | |
| 1.20.87 | 3 / 0 | |
| 1.20.86 | 3 / 0 | |
| 1.20.85 | 3 / 0 | |
| 1.20.84 | 3 / 0 | |
| 1.20.83 | 3 / 0 | |
| 1.20.82 | 3 / 0 | |
| 1.20.81 | 3 / 0 | |
| 1.20.80 | 3 / 0 | |
| 1.20.79 | 3 / 0 | |
| 1.20.78 | 3 / 0 | |
| 1.20.77 | 3 / 0 | |
| 1.20.76 | 3 / 0 | |
| 1.20.75 | 3 / 0 | |
| 1.20.74 | 3 / 0 | |
| 1.20.73 | 3 / 0 | |
| 1.20.72 | 3 / 0 | |
| 1.20.71 | 3 / 0 | |
| 1.20.70 | 3 / 0 | |
| 1.20.69 | 3 / 0 | |
| 1.20.68 | 3 / 0 | |
| 1.20.67 | 3 / 0 | |
| 1.20.66 | 3 / 0 | |
| 1.20.65 | 3 / 0 | |
| 1.20.64 | 3 / 0 | |
| 1.20.63 | 3 / 0 | |
| 1.20.62 | 3 / 0 | |
| 1.20.61 | 3 / 0 | |
| 1.20.60 | 3 / 0 | |
| 1.20.59 | 3 / 0 | |
| 1.20.57 | 3 / 0 | |
| 1.20.56 | 3 / 0 | |
| 1.20.55 | 3 / 0 | |
| 1.20.54 | 3 / 0 | |
| 1.20.53 | 3 / 0 | |
| 1.20.52 | 3 / 0 | |
| 1.20.51 | 3 / 0 | |
| 1.20.50 | 3 / 0 | |
| 1.20.49 | 3 / 0 | |
| 1.20.48 | 3 / 0 | |
| 1.20.47 | 3 / 0 | |
| 1.20.46 | 3 / 0 |
v1.32.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.32.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.20.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.