@dynamic-labs-wallet/node
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@dynamic-labs/sdk-api-core | AI (phantom-deps): Declared dep used transitively or in config; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @dynamic-labs-wallet/node is not a typosquat of zod; false positive on edit distance. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): MPC executor native binaries for wallet crypto operations; expected for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard base64-to-bytes helper for crypto operations. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): EVM message hex parsing for keccak256 hashing; standard wallet SDK pattern. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Native addon loader selecting platform-specific .node binary; standard pattern. | ai |
Versions (showing 50 of 251)
| Version | Deps | Published |
|---|---|---|
| 0.0.241 | 6 / 0 | |
| 0.0.240 | 6 / 0 | |
| 0.0.239 | 6 / 0 | |
| 0.0.238 | 6 / 0 | |
| 0.0.237 | 6 / 0 | |
| 0.0.236 | 6 / 0 | |
| 0.0.235 | 6 / 0 | |
| 0.0.234 | 6 / 0 | |
| 0.0.233 | 6 / 0 | |
| 0.0.232 | 6 / 0 | |
| 0.0.231 | 6 / 0 | |
| 0.0.230 | 6 / 0 | |
| 0.0.229 | 6 / 0 | |
| 0.0.228 | 6 / 0 | |
| 0.0.227 | 6 / 0 | |
| 0.0.226 | 6 / 0 | |
| 0.0.225 | 6 / 0 | |
| 0.0.224 | 6 / 0 | |
| 0.0.223 | 6 / 0 | |
| 0.0.222 | 6 / 0 | |
| 0.0.221 | 6 / 0 | |
| 0.0.220 | 6 / 0 | |
| 0.0.219 | 6 / 0 | |
| 0.0.218 | 6 / 0 | |
| 0.0.217 | 6 / 0 | |
| 0.0.216 | 6 / 0 | |
| 0.0.215 | 6 / 0 | |
| 0.0.214 | 6 / 0 | |
| 0.0.213 | 6 / 0 | |
| 0.0.212 | 6 / 0 | |
| 0.0.211 | 6 / 0 | |
| 0.0.210 | 6 / 0 | |
| 0.0.209 | 6 / 0 | |
| 0.0.208 | 6 / 0 | |
| 0.0.207 | 6 / 0 | |
| 0.0.206 | 6 / 0 | |
| 0.0.205 | 6 / 0 | |
| 0.0.204 | 6 / 0 | |
| 0.0.203 | 6 / 0 | |
| 0.0.202 | 6 / 0 | |
| 0.0.201 | 6 / 0 | |
| 0.0.200 | 6 / 0 | |
| 0.0.199 | 6 / 0 | |
| 0.0.198 | 6 / 0 | |
| 0.0.197 | 6 / 0 | |
| 0.0.196 | 6 / 0 | |
| 0.0.195 | 6 / 0 | |
| 0.0.194 | 6 / 0 | |
| 0.0.193 | 6 / 0 | |
| 0.0.192 | 6 / 0 |
v0.0.241
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.240
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.239
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.238
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.237
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.234
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.233
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.231
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.224
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.222
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.221
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.220
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.219
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.218
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.217
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.216
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.215
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.214
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.213
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.212
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.211
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.210
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.209
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.208
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.207
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.206
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.205
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.204
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.203
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.202
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.201
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.200
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.199
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.198
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.197
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.196
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.195
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.194
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.193
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.192
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.