@dynamic-labs-wallet/browser
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 |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Fires in wasm-bindgen generated glue code (libmpc_executor.js); expected pattern for WASM MPC crypto library. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Same wasm-bindgen generated file; new Function() is standard in WASM JS glue output. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode used for binary data handling in crypto/wallet SDK; no exfiltration context. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decode used for EVM message formatting (keccak256 hashing); standard wallet SDK pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established org package under Dynamic Labs; missing metadata is a style choice, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:@dynamic-labs-wallet/forward-mpc-client | AI (phantom-deps): Same org scope; likely re-exported or used indirectly through bundled output. | ai |
Versions (showing 16 of 318)
| Version | Deps | Published |
|---|---|---|
| 0.0.81 | 4 / 0 | |
| 0.0.80 | 4 / 0 | |
| 0.0.79 | 4 / 0 | |
| 0.0.78 | 4 / 0 | |
| 0.0.77 | 4 / 0 | |
| 0.0.76 | 4 / 0 | |
| 0.0.75 | 4 / 0 | |
| 0.0.74 | 5 / 0 | |
| 0.0.73 | 5 / 0 | |
| 0.0.72 | 3 / 0 | |
| 0.0.71 | 3 / 0 | |
| 0.0.70 | 4 / 0 | |
| 0.0.69 | 4 / 0 | |
| 0.0.68 | 4 / 0 | |
| 0.0.67 | 4 / 0 | |
| 0.0.66 | 4 / 0 |
v0.0.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.