@dynamic-labs-wallet/node-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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Entire @dynamic-labs-wallet namespace publishes without Sigstore provenance; consistent across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo-published SDK package; missing metadata is a style choice, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this scoped package family; not a risk indicator. | ai |
Versions (showing 25 of 139)
| Version | Deps | Published |
|---|---|---|
| 0.0.279 | 8 / 3 | |
| 0.0.278 | 8 / 3 | |
| 0.0.277 | 8 / 3 | |
| 0.0.276 | 8 / 3 | |
| 0.0.275 | 8 / 3 | |
| 0.0.274 | 8 / 3 | |
| 0.0.273 | 8 / 3 | |
| 0.0.272 | 8 / 3 | |
| 0.0.271 | 8 / 3 | |
| 0.0.270 | 8 / 3 | |
| 0.0.269 | 8 / 3 | |
| 0.0.268 | 8 / 3 | |
| 0.0.267 | 8 / 3 | |
| 0.0.266 | 8 / 3 | |
| 0.0.265 | 8 / 3 | |
| 0.0.264 | 8 / 3 | |
| 0.0.263 | 8 / 3 | |
| 0.0.262 | 8 / 3 | |
| 0.0.261 | 8 / 3 | |
| 0.0.260 | 8 / 3 | |
| 0.0.259 | 8 / 3 | |
| 0.0.258 | 8 / 3 | |
| 0.0.257 | 8 / 3 | |
| 0.0.256 | 8 / 3 | |
| 0.0.255 | 8 / 3 |
v0.0.279
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.278
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.277
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.276
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.275
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.274
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.273
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.272
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.271
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.270
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.269
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.268
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.267
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.266
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.265
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.264
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.263
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.262
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.261
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.260
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.259
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.258
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.257
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.256
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.255
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.