@suilend/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, 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:@7kprotocol/sdk-ts | AI (dependencies): 7k Protocol is a legitimate Sui ecosystem swap aggregator; its SDK is a natural dependency for @suilend/sdk's swap functionality. | ai | |
| dependencies | unvetted-dep:@flowx-finance/sdk | AI (dependencies): FlowX Finance is a known Sui ecosystem DEX/aggregator; its SDK is a legitimate dependency for swap routing in a Sui DeFi lending SDK. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 112 versions and 741-day history; lack of provenance is common and not a disqualifying signal here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Suilend SDK is a legitimate DeFi protocol SDK; sparse README and missing keywords are cosmetic issues, not spam indicators. | ai | |
| phantom-deps | phantom-dep:crypto-js | AI (phantom-deps): crypto-js declared in dependencies but not directly imported; minor packaging hygiene issue, not a security risk for this SDK. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 11 / 6 | |
| 3.0.8 | 11 / 3 | |
| 3.0.7 | 10 / 3 | |
| 3.0.6 | 10 / 3 | |
| 3.0.5 | 10 / 3 | |
| 3.0.4 | 10 / 3 | |
| 3.0.3 | 11 / 3 | |
| 3.0.2 | 11 / 3 | |
| 3.0.1 | 11 / 3 | |
| 2.0.7 | 11 / 3 | |
| 2.0.6 | 11 / 3 | |
| 2.0.5 | 11 / 3 | |
| 2.0.4 | 11 / 3 | |
| 2.0.3 | 11 / 3 | |
| 2.0.2 | 11 / 3 | |
| 2.0.1 | 11 / 3 | |
| 2.0.0 | 11 / 3 | |
| 1.1.99 | 11 / 3 | |
| 1.1.98 | 11 / 3 | |
| 1.1.97 | 11 / 3 | |
| 1.1.95 | 11 / 3 | |
| 1.1.90 | 12 / 3 |
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.