@suilend/frontend-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@msafe/sui-wallet | AI (dependencies): Legitimate Sui wallet SDK, fits package's wallet-integration purpose. | ai | |
| dependencies | unvetted-dep:@msafe/sui3-utils | AI (dependencies): Companion utils package to msafe wallet SDK, benign. | ai | |
| dependencies | unvetted-dep:@msafe/sui-app-store | AI (dependencies): Companion package to msafe wallet integration, benign. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Standard peer dep used via JSX/config, false positive. | ai | |
| phantom-deps | phantom-dep:@msafe/sui3-utils | AI (phantom-deps): Used in config/build, not a real concern. | ai | |
| phantom-deps | phantom-dep:@msafe/sui-app-store | AI (phantom-deps): Used in config/build, not a real concern. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.2.72 | 6 / 14 | |
| 0.1.8 | 16 / 14 | |
| 0.1.5 | 16 / 14 | |
| 0.1.2 | 16 / 14 | |
| 0.1.1 | 12 / 14 | |
| 0.1.0 | 12 / 14 |
v0.2.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.