@suilend/springsui-sdk
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:@mysten/sui-v1 | AI (dependencies): @mysten/sui-v1 is an npm alias for @mysten/sui (official Mysten Labs Sui SDK). This aliasing pattern is standard for multi-version coexistence and is not a security concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Short README and no keywords are cosmetic issues; this is a legitimate developer SDK for the Suilend/SpringSui protocol, not spam. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.0.4 | 1 / 1 | |
| 3.0.3 | 1 / 1 | |
| 3.0.2 | 1 / 1 | |
| 3.0.1 | 1 / 1 | |
| 3.0.0 | 1 / 1 | |
| 2.0.2 | 1 / 1 | |
| 2.0.1 | 1 / 1 | |
| 2.0.0 | 1 / 1 | |
| 1.0.29 | 2 / 1 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.