@dynamic-labs-wallet/btc-utils
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:internal/core/ed_bls12_377.js | AI (source-diff): ESM variant of same minified bundle; same rationale as .cjs counterpart. | ai | |
| source-diff | obfuscated-file:internal/core/ed_bls12_377.cjs | AI (source-diff): Minified bundle output for MPC crypto library; readable logic, not obfuscated malware. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing is consistent with org-level automation; no malicious indicators. | ai | |
| source-diff | obfuscated-file:internal/core/ed25519_exportable.cjs | AI (source-diff): Standard minified TypeScript CJS output; samples show clean MPC crypto class, no malicious patterns. | ai | |
| source-diff | obfuscated-file:internal/core/bip340.cjs | AI (source-diff): Standard minified TypeScript CJS output; samples show clean MPC crypto class, no malicious patterns. | ai | |
| source-diff | obfuscated-file:internal/core/ecdsa.cjs | AI (source-diff): Standard minified TypeScript CJS output; samples show clean MPC crypto class, no malicious patterns. | ai | |
| source-diff | obfuscated-file:internal/core/ed25519.cjs | AI (source-diff): Standard minified TypeScript CJS output; samples show clean MPC crypto class, no malicious patterns. | ai | |
| source-diff | obfuscated-file:internal/core/sr25519.cjs | AI (source-diff): Standard minified TypeScript CJS output; samples show clean MPC crypto class, no malicious patterns. | ai | |
| source-diff | obfuscated-file:internal/core/types.cjs | AI (source-diff): Standard minified TypeScript CJS output; samples show clean type definitions, no malicious patterns. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Publisher is a known org with 836 approved packages; 0.0.0 is a monorepo placeholder pattern. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding of public keys is standard in Bitcoin/crypto libraries; not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package published via CI; missing metadata is consistent across all 100 versions. | ai |
Versions (showing 51 of 149)
| Version | Deps | Published |
|---|---|---|
| 1.0.86 | 5 / 2 | |
| 1.0.85 | 5 / 2 | |
| 1.0.84 | 5 / 2 | |
| 1.0.83 | 5 / 2 | |
| 1.0.82 | 5 / 2 | |
| 1.0.81 | 5 / 2 | |
| 1.0.80 | 5 / 2 | |
| 1.0.79 | 5 / 2 | |
| 1.0.78 | 5 / 2 | |
| 1.0.77 | 5 / 2 | |
| 1.0.76 | 5 / 2 | |
| 1.0.75 | 5 / 2 | |
| 1.0.74 | 5 / 2 | |
| 1.0.73 | 5 / 2 | |
| 1.0.72 | 5 / 2 | |
| 1.0.71 | 5 / 2 | |
| 1.0.70 | 5 / 2 | |
| 1.0.69 | 5 / 2 | |
| 1.0.68 | 5 / 2 | |
| 1.0.67 | 5 / 2 | |
| 1.0.66 | 5 / 2 | |
| 1.0.65 | 5 / 2 | |
| 1.0.64 | 5 / 2 | |
| 1.0.63 | 5 / 2 | |
| 1.0.62 | 5 / 2 | |
| 1.0.61 | 5 / 2 | |
| 1.0.60 | 5 / 2 | |
| 1.0.59 | 5 / 2 | |
| 1.0.58 | 5 / 2 | |
| 1.0.57 | 5 / 2 | |
| 1.0.56 | 5 / 2 | |
| 1.0.55 | 5 / 2 | |
| 1.0.54 | 5 / 2 | |
| 1.0.53 | 5 / 2 | |
| 1.0.52 | 5 / 2 | |
| 1.0.51 | 5 / 2 | |
| 1.0.50 | 5 / 2 | |
| 1.0.49 | 5 / 2 | |
| 1.0.48 | 5 / 2 | |
| 1.0.47 | 5 / 2 | |
| 1.0.46 | 5 / 2 | |
| 1.0.45 | 5 / 2 | |
| 1.0.44 | 5 / 2 | |
| 1.0.43 | 5 / 2 | |
| 1.0.42 | 5 / 2 | |
| 1.0.41 | 5 / 2 | |
| 1.0.40 | 5 / 2 | |
| 1.0.39 | 5 / 2 | |
| 1.0.38 | 5 / 2 | |
| 1.0.37 | 5 / 2 | |
| 1.0.36 | 5 / 2 |
v1.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.