@kamino-finance/kswap-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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): 82-version SDK from Kamino Finance; missing metadata is a style issue, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established SDK package; missing description is cosmetic and stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions; no provenance attestation but no other risk signals present. | ai | |
| phantom-deps | phantom-dep:dotenv-expand | AI (phantom-deps): dotenv-expand used in config files, not directly imported — stable false positive. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decoding Jupiter instruction data from base64 is standard Solana SDK usage, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@types/crypto-js | AI (phantom-deps): Type-only package loaded by convention, not directly imported — stable false positive. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv is a declared dep used in config/env setup, not directly imported in source — stable false positive. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): winston is a declared dep used for logging config, not directly imported — stable false positive. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.8.1 | 15 / 1 | |
| 2.8.0 | 15 / 1 | |
| 2.7.2 | 15 / 1 | |
| 2.7.1 | 15 / 1 | |
| 2.7.0 | 15 / 1 | |
| 2.6.1 | 15 / 1 | |
| 2.6.0 | 15 / 1 | |
| 2.5.0 | 15 / 1 | |
| 2.4.5 | 15 / 0 | |
| 2.4.4 | 15 / 0 | |
| 2.4.3 | 15 / 0 | |
| 2.4.2 | 15 / 0 | |
| 2.4.1 | 15 / 0 | |
| 2.4.0 | 15 / 0 | |
| 2.3.0 | 15 / 0 | |
| 2.2.1 | 15 / 0 | |
| 2.2.0 | 15 / 0 | |
| 2.1.2 | 15 / 0 | |
| 2.1.1 | 15 / 0 | |
| 2.1.0 | 15 / 0 | |
| 2.0.0 | 15 / 0 |
v2.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.