@dynamic-labs-wallet/sui
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Metadata gaps are consistent across the entire @dynamic-labs-wallet package family; not indicative of spam/malice. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across all @dynamic-labs-wallet scoped packages; not a malice signal here. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @dynamic-labs-wallet/sui; Levenshtein match to 'uuid' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @dynamic-labs-wallet/sui; Levenshtein match to 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @dynamic-labs-wallet/sui; Levenshtein match to 'yup' is a false positive. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used for Sui transaction bytes — standard blockchain wallet operation, not obfuscation. | ai |
Versions (showing 17 of 217)
| Version | Deps | Published |
|---|---|---|
| 0.0.72 | 3 / 0 | |
| 0.0.71 | 3 / 0 | |
| 0.0.70 | 3 / 0 | |
| 0.0.69 | 3 / 0 | |
| 0.0.68 | 3 / 0 | |
| 0.0.67 | 3 / 0 | |
| 0.0.66 | 3 / 0 | |
| 0.0.65 | 3 / 0 | |
| 0.0.64 | 3 / 0 | |
| 0.0.63 | 3 / 0 | |
| 0.0.62 | 3 / 0 | |
| 0.0.61 | 3 / 0 | |
| 0.0.60 | 3 / 0 | |
| 0.0.59 | 3 / 0 | |
| 0.0.58 | 3 / 0 | |
| 0.0.57 | 3 / 0 | |
| 0.0.56 | 3 / 0 |
v0.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.