@dynamic-labs-wallet/btc
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across @dynamic-labs-wallet org packages; not a spam indicator here. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; no provenance attestation but consistent with org publishing pattern. | ai | |
| phantom-deps | phantom-dep:@dynamic-labs/sdk-api-core | AI (phantom-deps): Declared as peer/transitive dep; phantom-dep heuristic false positive for config-only references. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Bitcoin PSBT construction from txHex is standard bitcoinjs-lib usage; not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package; missing metadata is consistent across all @dynamic-labs-wallet/* releases. | ai |
Versions (showing 100 of 196)
| Version | Deps | Published |
|---|---|---|
| 1.0.87 | 5 / 0 | |
| 1.0.86 | 5 / 0 | |
| 1.0.85 | 5 / 0 | |
| 1.0.84 | 5 / 0 | |
| 1.0.83 | 5 / 0 | |
| 1.0.82 | 5 / 0 | |
| 1.0.81 | 5 / 0 | |
| 1.0.80 | 5 / 0 | |
| 1.0.79 | 5 / 0 | |
| 1.0.78 | 5 / 0 | |
| 1.0.77 | 5 / 0 | |
| 1.0.76 | 5 / 0 | |
| 1.0.75 | 5 / 0 | |
| 1.0.74 | 5 / 0 | |
| 1.0.73 | 5 / 0 | |
| 1.0.72 | 5 / 0 | |
| 1.0.71 | 5 / 0 | |
| 1.0.70 | 5 / 0 | |
| 1.0.69 | 5 / 0 | |
| 1.0.68 | 5 / 0 | |
| 1.0.67 | 5 / 0 | |
| 1.0.66 | 5 / 0 | |
| 1.0.65 | 5 / 0 | |
| 1.0.64 | 5 / 0 | |
| 1.0.63 | 5 / 0 | |
| 1.0.62 | 5 / 0 | |
| 1.0.61 | 5 / 0 | |
| 1.0.60 | 5 / 0 | |
| 1.0.59 | 5 / 0 | |
| 1.0.58 | 5 / 0 | |
| 1.0.57 | 5 / 0 | |
| 1.0.56 | 5 / 0 | |
| 1.0.55 | 5 / 0 | |
| 1.0.54 | 5 / 0 | |
| 1.0.53 | 5 / 0 | |
| 1.0.52 | 5 / 0 | |
| 1.0.51 | 5 / 0 | |
| 1.0.50 | 5 / 0 | |
| 1.0.49 | 5 / 0 | |
| 1.0.48 | 5 / 0 | |
| 1.0.47 | 5 / 0 | |
| 1.0.46 | 5 / 0 | |
| 1.0.45 | 5 / 0 | |
| 1.0.44 | 5 / 0 | |
| 1.0.43 | 5 / 0 | |
| 1.0.42 | 5 / 0 | |
| 1.0.41 | 5 / 0 | |
| 1.0.40 | 5 / 0 | |
| 1.0.39 | 5 / 0 | |
| 1.0.38 | 5 / 0 | |
| 1.0.37 | 5 / 0 | |
| 1.0.36 | 5 / 0 | |
| 1.0.35 | 5 / 0 | |
| 1.0.34 | 5 / 0 | |
| 1.0.33 | 5 / 0 | |
| 1.0.32 | 5 / 0 | |
| 1.0.31 | 5 / 0 | |
| 1.0.30 | 5 / 0 | |
| 1.0.29 | 5 / 0 | |
| 1.0.28 | 5 / 0 | |
| 1.0.27 | 5 / 0 | |
| 1.0.26 | 5 / 0 | |
| 1.0.25 | 5 / 0 | |
| 1.0.24 | 5 / 0 | |
| 1.0.23 | 5 / 0 | |
| 1.0.22 | 5 / 0 | |
| 1.0.21 | 5 / 0 | |
| 1.0.20 | 5 / 0 | |
| 1.0.19 | 5 / 0 | |
| 1.0.18 | 5 / 0 | |
| 1.0.17 | 5 / 0 | |
| 1.0.16 | 5 / 0 | |
| 1.0.15 | 5 / 0 | |
| 1.0.14 | 5 / 0 | |
| 1.0.13 | 5 / 0 | |
| 1.0.12 | 5 / 0 | |
| 1.0.11 | 5 / 0 | |
| 1.0.10 | 5 / 0 | |
| 1.0.9 | 5 / 0 | |
| 1.0.8 | 5 / 0 | |
| 1.0.7 | 5 / 0 | |
| 1.0.6 | 5 / 0 | |
| 1.0.5 | 5 / 0 | |
| 1.0.4 | 5 / 0 | |
| 1.0.3 | 5 / 0 | |
| 1.0.2 | 5 / 0 | |
| 1.0.1 | 5 / 0 | |
| 1.0.0 | 5 / 0 | |
| 0.0.354 | 5 / 0 | |
| 0.0.353 | 5 / 0 | |
| 0.0.352 | 5 / 0 | |
| 0.0.351 | 5 / 0 | |
| 0.0.350 | 5 / 0 | |
| 0.0.349 | 5 / 0 | |
| 0.0.348 | 5 / 0 | |
| 0.0.347 | 5 / 0 | |
| 0.0.346 | 5 / 0 | |
| 0.0.345 | 5 / 0 | |
| 0.0.344 | 5 / 0 | |
| 0.0.343 | 5 / 0 |
v1.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.