@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, 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 |
|---|---|---|---|---|
| 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 51 of 186)
| Version | Deps | Published |
|---|---|---|
| 1.0.86 | 3 / 1 | |
| 1.0.85 | 3 / 1 | |
| 1.0.84 | 3 / 1 | |
| 1.0.83 | 3 / 1 | |
| 1.0.82 | 3 / 1 | |
| 1.0.81 | 3 / 1 | |
| 1.0.80 | 3 / 1 | |
| 1.0.79 | 3 / 1 | |
| 1.0.78 | 3 / 1 | |
| 1.0.77 | 3 / 1 | |
| 1.0.76 | 3 / 1 | |
| 1.0.75 | 3 / 1 | |
| 1.0.74 | 3 / 1 | |
| 1.0.73 | 3 / 1 | |
| 1.0.72 | 3 / 1 | |
| 1.0.71 | 3 / 1 | |
| 1.0.70 | 3 / 1 | |
| 1.0.69 | 3 / 1 | |
| 1.0.68 | 3 / 1 | |
| 1.0.67 | 3 / 1 | |
| 1.0.66 | 3 / 1 | |
| 1.0.65 | 3 / 1 | |
| 1.0.64 | 3 / 1 | |
| 1.0.63 | 3 / 1 | |
| 1.0.62 | 3 / 1 | |
| 1.0.61 | 3 / 1 | |
| 1.0.60 | 3 / 1 | |
| 1.0.59 | 3 / 1 | |
| 1.0.58 | 3 / 1 | |
| 1.0.57 | 3 / 1 | |
| 1.0.56 | 3 / 1 | |
| 1.0.55 | 3 / 1 | |
| 1.0.54 | 3 / 1 | |
| 1.0.53 | 3 / 1 | |
| 1.0.52 | 3 / 1 | |
| 1.0.51 | 3 / 1 | |
| 1.0.50 | 3 / 1 | |
| 1.0.49 | 3 / 1 | |
| 1.0.48 | 3 / 1 | |
| 1.0.47 | 3 / 1 | |
| 1.0.46 | 3 / 1 | |
| 1.0.45 | 3 / 1 | |
| 1.0.44 | 3 / 1 | |
| 1.0.43 | 3 / 1 | |
| 1.0.42 | 3 / 1 | |
| 1.0.41 | 3 / 1 | |
| 1.0.40 | 3 / 1 | |
| 1.0.39 | 3 / 1 | |
| 1.0.38 | 3 / 1 | |
| 1.0.37 | 3 / 1 | |
| 1.0.36 | 3 / 1 |
v1.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.