@dynamic-labs-wallet/node-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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Monorepo package; missing description is consistent across the entire @dynamic-labs-wallet namespace. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Part of a large established monorepo; 0.0.0 is a placeholder convention for this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal library in a monorepo; missing metadata is expected, not a spam indicator. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used for public key bytes in TON address derivation — standard cryptographic usage, not obfuscation. | ai |
Versions (showing 17 of 139)
| Version | Deps | Published |
|---|---|---|
| 0.0.271 | 6 / 1 | |
| 0.0.270 | 6 / 1 | |
| 0.0.269 | 6 / 1 | |
| 0.0.268 | 6 / 1 | |
| 0.0.267 | 6 / 1 | |
| 0.0.266 | 6 / 1 | |
| 0.0.265 | 6 / 1 | |
| 0.0.263 | 6 / 1 | |
| 0.0.262 | 6 / 1 | |
| 0.0.261 | 6 / 1 | |
| 0.0.260 | 6 / 1 | |
| 0.0.259 | 6 / 1 | |
| 0.0.258 | 6 / 1 | |
| 0.0.257 | 6 / 1 | |
| 0.0.256 | 6 / 1 | |
| 0.0.255 | 6 / 1 | |
| 0.0.0 | 0 / 0 |
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. 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. 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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.