@dynamic-labs-wallet/ton
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:hex-decode | AI (semgrep): Hex decoding is standard public-key parsing for TON blockchain address derivation; not obfuscation. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped package @dynamic-labs-wallet/ton; 'ton' suffix match to 'koa' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @dynamic-labs-wallet/ton; 'ton' suffix match to 'got' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @dynamic-labs-wallet/ton; 'ton' suffix match to 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @dynamic-labs-wallet/ton; 'ton' suffix match to 'zod' is a false positive. | ai |
Versions (showing 54 of 165)
| Version | Deps | Published |
|---|---|---|
| 0.0.283 | 4 / 0 | |
| 0.0.282 | 4 / 0 | |
| 0.0.281 | 4 / 0 | |
| 0.0.280 | 4 / 0 | |
| 0.0.279 | 4 / 0 | |
| 0.0.278 | 4 / 0 | |
| 0.0.277 | 4 / 0 | |
| 0.0.276 | 4 / 0 | |
| 0.0.275 | 4 / 0 | |
| 0.0.274 | 4 / 0 | |
| 0.0.273 | 4 / 0 | |
| 0.0.272 | 4 / 0 | |
| 0.0.271 | 4 / 0 | |
| 0.0.270 | 4 / 0 | |
| 0.0.269 | 4 / 0 | |
| 0.0.268 | 4 / 0 | |
| 0.0.267 | 4 / 0 | |
| 0.0.266 | 4 / 0 | |
| 0.0.265 | 4 / 0 | |
| 0.0.264 | 4 / 0 | |
| 0.0.263 | 4 / 0 | |
| 0.0.262 | 4 / 0 | |
| 0.0.261 | 4 / 0 | |
| 0.0.260 | 4 / 0 | |
| 0.0.259 | 4 / 0 | |
| 0.0.258 | 4 / 0 | |
| 0.0.257 | 4 / 0 | |
| 0.0.256 | 4 / 0 | |
| 0.0.255 | 4 / 0 | |
| 0.0.254 | 4 / 0 | |
| 0.0.253 | 4 / 0 | |
| 0.0.252 | 4 / 0 | |
| 0.0.251 | 4 / 0 | |
| 0.0.250 | 4 / 0 | |
| 0.0.249 | 4 / 0 | |
| 0.0.248 | 4 / 0 | |
| 0.0.247 | 4 / 0 | |
| 0.0.246 | 4 / 0 | |
| 0.0.245 | 4 / 0 | |
| 0.0.244 | 4 / 0 | |
| 0.0.243 | 4 / 0 | |
| 0.0.242 | 4 / 0 | |
| 0.0.241 | 4 / 0 | |
| 0.0.240 | 4 / 0 | |
| 0.0.239 | 4 / 0 | |
| 0.0.238 | 4 / 0 | |
| 0.0.237 | 4 / 0 | |
| 0.0.236 | 4 / 0 | |
| 0.0.235 | 4 / 0 | |
| 0.0.234 | 4 / 0 | |
| 0.0.233 | 4 / 0 | |
| 0.0.232 | 4 / 0 | |
| 0.0.231 | 4 / 0 | |
| 0.0.230 | 3 / 0 |
v0.0.283
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.282
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.281
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.280
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.279
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.278
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.277
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.276
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.275
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.274
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.273
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.272
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.271
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.270
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.269
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.268
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.267
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.266
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.265
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.264
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.263
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.262
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.261
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.260
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.259
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.258
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.257
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.256
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.255
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.254
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.253
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.252
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.251
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.250
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.249
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.248
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.247
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.246
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.245
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.244
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.243
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.242
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.241
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.240
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.239
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.238
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.237
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.236
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.235
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.234
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.