@suilend/sui-fe
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:mixpanel-browser | AI (dependencies): mixpanel-browser is a legitimate, widely-used analytics SDK. Its use is appropriate for a frontend library with a tracking module (lib/track.js). | ai | |
| phantom-deps | phantom-dep:next | AI (phantom-deps): next is used via eslint-config-next in devDependencies and referenced in config files; phantom-dep detection is a known false positive for this usage pattern. | ai | |
| phantom-deps | phantom-dep:@mysten/wallet-standard | AI (phantom-deps): Declared as a dependency and referenced in config/type files; phantom-dep heuristic fires on indirect usage patterns common in Sui ecosystem packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package uses named exports map with no default entry point; near-empty index.js and minimal README are consistent with this library's design pattern, not spam. | ai | |
| dependencies | unvetted-dep:blake2b | AI (dependencies): blake2b is a well-known cryptographic hashing library; appropriate for a Sui blockchain frontend utility package. | ai | |
| dependencies | unvetted-dep:@mysten/wallet-standard | AI (dependencies): @mysten/wallet-standard is the official Mysten Labs wallet standard package, expected in Sui ecosystem libraries. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 3.0.7 | 5 / 13 | |
| 3.0.6 | 5 / 13 | |
| 3.0.5 | 5 / 13 | |
| 3.0.4 | 5 / 13 | |
| 3.0.3 | 5 / 13 | |
| 3.0.2 | 5 / 13 | |
| 3.0.1 | 5 / 13 | |
| 3.0.0 | 5 / 13 | |
| 2.0.13 | 5 / 13 | |
| 2.0.12 | 5 / 13 | |
| 2.0.11 | 5 / 13 | |
| 2.0.10 | 5 / 13 | |
| 2.0.9 | 5 / 13 | |
| 2.0.8 | 5 / 13 | |
| 2.0.7 | 5 / 13 | |
| 2.0.6 | 5 / 13 | |
| 2.0.5 | 5 / 13 | |
| 2.0.4 | 5 / 13 | |
| 2.0.3 | 5 / 13 | |
| 2.0.2 | 5 / 13 | |
| 2.0.1 | 5 / 13 | |
| 2.0.0 | 5 / 13 | |
| 0.4.11 | 5 / 13 | |
| 0.4.10 | 5 / 13 | |
| 0.4.9 | 5 / 13 | |
| 0.4.8 | 5 / 13 | |
| 0.4.7 | 5 / 13 | |
| 0.4.6 | 5 / 13 | |
| 0.4.5 | 5 / 13 | |
| 0.4.4 | 5 / 13 | |
| 0.4.3 | 5 / 13 | |
| 0.4.2 | 5 / 13 | |
| 0.4.1 | 5 / 13 | |
| 0.4.0 | 5 / 13 | |
| 0.3.57 | 5 / 13 | |
| 0.3.56 | 5 / 13 | |
| 0.3.55 | 5 / 13 | |
| 0.3.54 | 5 / 13 | |
| 0.3.53 | 5 / 13 | |
| 0.3.52 | 5 / 13 | |
| 0.3.51 | 5 / 13 | |
| 0.3.50 | 5 / 13 | |
| 0.3.49 | 5 / 13 | |
| 0.3.48 | 5 / 13 | |
| 0.3.47 | 5 / 13 | |
| 0.3.46 | 7 / 14 | |
| 0.3.45 | 7 / 14 | |
| 0.3.44 | 7 / 14 | |
| 0.3.43 | 7 / 14 | |
| 0.3.42 | 7 / 14 | |
| 0.3.41 | 7 / 14 |
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.