@kamino-finance/klend-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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:anchor-client-gen | AI (npm-metadata): devDependency used only for codegen; not included in published dist. SHA-pin is actually safer than a floating version. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard Solana account data deserialization pattern; not obfuscation or payload hiding. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP is 127.0.0.1 (localhost) for local Solana test validator; not a remote exfiltration endpoint. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 8.0.2 | 20 / 34 | |
| 8.0.1 | 20 / 34 | |
| 8.0.0 | 20 / 34 | |
| 7.3.22 | 20 / 34 |
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
2 findingsDependency 'anchor-client-gen' in `devDependencies` points to 'git+https://github.com/kklas/anchor-client-gen.git#03a3273a10b804a41878e71cdae1b7d6257aa347' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.