@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 100 of 251)
| Version | Deps | Published |
|---|---|---|
| 0.0.341 | 7 / 0 | |
| 0.0.340 | 7 / 0 | |
| 0.0.339 | 7 / 0 | |
| 0.0.338 | 7 / 0 | |
| 0.0.337 | 7 / 0 | |
| 0.0.336 | 7 / 0 | |
| 0.0.335 | 6 / 0 | |
| 0.0.334 | 6 / 0 | |
| 0.0.333 | 6 / 0 | |
| 0.0.332 | 6 / 0 | |
| 0.0.331 | 6 / 0 | |
| 0.0.330 | 6 / 0 | |
| 0.0.329 | 6 / 0 | |
| 0.0.328 | 6 / 0 | |
| 0.0.327 | 6 / 0 | |
| 0.0.326 | 6 / 0 | |
| 0.0.325 | 6 / 0 | |
| 0.0.324 | 6 / 0 | |
| 0.0.323 | 6 / 0 | |
| 0.0.322 | 6 / 0 | |
| 0.0.321 | 6 / 0 | |
| 0.0.320 | 6 / 0 | |
| 0.0.319 | 6 / 0 | |
| 0.0.318 | 6 / 0 | |
| 0.0.317 | 6 / 0 | |
| 0.0.316 | 6 / 0 | |
| 0.0.315 | 6 / 0 | |
| 0.0.314 | 6 / 0 | |
| 0.0.313 | 6 / 0 | |
| 0.0.312 | 6 / 0 | |
| 0.0.311 | 6 / 0 | |
| 0.0.310 | 6 / 0 | |
| 0.0.309 | 6 / 0 | |
| 0.0.308 | 6 / 0 | |
| 0.0.307 | 6 / 0 | |
| 0.0.306 | 6 / 0 | |
| 0.0.305 | 6 / 0 | |
| 0.0.304 | 6 / 0 | |
| 0.0.303 | 6 / 0 | |
| 0.0.302 | 6 / 0 | |
| 0.0.301 | 6 / 0 | |
| 0.0.300 | 6 / 0 | |
| 0.0.299 | 6 / 0 | |
| 0.0.298 | 6 / 0 | |
| 0.0.297 | 6 / 0 | |
| 0.0.296 | 6 / 0 | |
| 0.0.295 | 6 / 0 | |
| 0.0.294 | 6 / 0 | |
| 0.0.293 | 6 / 0 | |
| 0.0.292 | 6 / 0 | |
| 0.0.291 | 6 / 0 | |
| 0.0.290 | 6 / 0 | |
| 0.0.289 | 6 / 0 | |
| 0.0.288 | 6 / 0 | |
| 0.0.287 | 6 / 0 | |
| 0.0.286 | 6 / 0 | |
| 0.0.285 | 6 / 0 | |
| 0.0.284 | 6 / 0 | |
| 0.0.283 | 6 / 0 | |
| 0.0.282 | 6 / 0 | |
| 0.0.281 | 6 / 0 | |
| 0.0.280 | 6 / 0 | |
| 0.0.279 | 6 / 0 | |
| 0.0.278 | 6 / 0 | |
| 0.0.277 | 6 / 0 | |
| 0.0.276 | 6 / 0 | |
| 0.0.275 | 6 / 0 | |
| 0.0.274 | 6 / 0 | |
| 0.0.273 | 6 / 0 | |
| 0.0.272 | 6 / 0 | |
| 0.0.271 | 6 / 0 | |
| 0.0.270 | 6 / 0 | |
| 0.0.269 | 6 / 0 | |
| 0.0.268 | 6 / 0 | |
| 0.0.267 | 6 / 0 | |
| 0.0.266 | 6 / 0 | |
| 0.0.265 | 6 / 0 | |
| 0.0.264 | 6 / 0 | |
| 0.0.263 | 6 / 0 | |
| 0.0.262 | 6 / 0 | |
| 0.0.261 | 6 / 0 | |
| 0.0.260 | 6 / 0 | |
| 0.0.259 | 6 / 0 | |
| 0.0.258 | 6 / 0 | |
| 0.0.257 | 6 / 0 | |
| 0.0.256 | 6 / 0 | |
| 0.0.255 | 6 / 0 | |
| 0.0.254 | 6 / 0 | |
| 0.0.253 | 6 / 0 | |
| 0.0.252 | 6 / 0 | |
| 0.0.251 | 6 / 0 | |
| 0.0.250 | 6 / 0 | |
| 0.0.249 | 6 / 0 | |
| 0.0.248 | 6 / 0 | |
| 0.0.247 | 6 / 0 | |
| 0.0.246 | 6 / 0 | |
| 0.0.245 | 6 / 0 | |
| 0.0.244 | 6 / 0 | |
| 0.0.243 | 6 / 0 | |
| 0.0.242 | 6 / 0 |
v0.0.320
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.319
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.318
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.317
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.316
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.315
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.314
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.313
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.312
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.311
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.310
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.309
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.308
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.307
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.306
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.305
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.304
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.303
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.302
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.301
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.300
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.299
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.298
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.297
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.296
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.295
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.294
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.293
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.292
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.291
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.290
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.289
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.288
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.287
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.286
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.285
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.284
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.283
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.282
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.281
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.280
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.279
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.278
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.277
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.276
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.275
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.274
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.273
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.272
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.271
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.270
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.269
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.268
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.267
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.266
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.265
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.264
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.263
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.262
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.261
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.260
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.259
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.256
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.255
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.254
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.253
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.252
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.251
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.250
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.249
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.248
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.247
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.246
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.245
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.244
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.243
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.242
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.