@dynamic-labs/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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @dynamic-labs/sui refers to Sui blockchain; not a typosquat of uuid. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @dynamic-labs/sui refers to Sui blockchain; not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @dynamic-labs/sui refers to Sui blockchain; not a typosquat of yup. | ai | |
| phantom-deps | phantom-dep:text-encoding | AI (phantom-deps): text-encoding is a declared runtime dep for Sui blockchain encoding; phantom-dep heuristic false positive. | ai |
Versions (showing 40 of 140)
| Version | Deps | Published |
|---|---|---|
| 4.19.5 | 11 / 0 | |
| 4.19.4 | 11 / 0 | |
| 4.19.3 | 11 / 0 | |
| 4.19.2 | 11 / 0 | |
| 4.19.1 | 11 / 0 | |
| 4.19.0 | 11 / 0 | |
| 4.18.8 | 11 / 0 | |
| 4.18.7 | 11 / 0 | |
| 4.18.6 | 11 / 0 | |
| 4.18.5 | 11 / 0 | |
| 4.18.4 | 11 / 0 | |
| 4.18.3 | 11 / 0 | |
| 4.18.2 | 11 / 0 | |
| 4.18.1 | 11 / 0 | |
| 4.18.0 | 11 / 0 | |
| 4.17.0 | 11 / 0 | |
| 4.16.0 | 11 / 0 | |
| 4.15.0 | 11 / 0 | |
| 4.14.0 | 11 / 0 | |
| 4.13.0 | 11 / 0 | |
| 4.12.4 | 11 / 0 | |
| 4.12.3 | 11 / 0 | |
| 4.12.2 | 11 / 0 | |
| 4.12.1 | 11 / 0 | |
| 4.12.0 | 11 / 0 | |
| 4.11.2 | 11 / 0 | |
| 4.11.1 | 11 / 0 | |
| 4.11.0 | 11 / 0 | |
| 4.10.4 | 11 / 0 | |
| 4.10.3 | 11 / 0 | |
| 4.10.2 | 11 / 0 | |
| 4.10.1 | 11 / 0 | |
| 4.10.0 | 11 / 0 | |
| 4.9.12 | 11 / 0 | |
| 4.9.11 | 11 / 0 | |
| 4.9.10 | 11 / 0 | |
| 4.9.9 | 10 / 0 | |
| 4.9.8 | 9 / 0 | |
| 4.9.7 | 9 / 0 | |
| 4.9.6 | 9 / 0 |
v4.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.