← Home

@kamino-finance/klend-sdk

npm Repository Homepage
40
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

kaminoadmin

Keywords

solanaanchorklendkamino

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): Publish shifted to CI/CD (GitHub Actions) account, no malicious diff vs prior version. ai
provenance publisher-changed AI (provenance): Change reflects CI/CD publishing pipeline adoption, not compromise. ai
phantom-deps phantom-dep:fzstd AI (phantom-deps): Used indirectly via config/codegen, not a real issue. ai
phantom-deps phantom-dep:@solana/buffer-layout AI (phantom-deps): Used indirectly via config/codegen, not a real issue. ai
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: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
semgrep semgrep:base64-decode AI (semgrep): Standard Solana account data deserialization pattern; not obfuscation or payload hiding. ai

Versions (showing 40 of 40)

Version Deps Published
9.1.6 20 / 34
9.1.5 20 / 34
9.1.4 20 / 34
9.1.3 20 / 34
9.1.2 20 / 34
9.1.1 20 / 34
9.1.0 20 / 34
9.0.2 20 / 34
9.0.1 20 / 34
9.0.0 20 / 34
8.1.0 20 / 34
8.0.3 20 / 34
8.0.2 20 / 34
8.0.1 20 / 34
8.0.0 20 / 34
7.3.22 20 / 34
7.3.21 20 / 34
7.3.20 20 / 34
7.3.19 20 / 34
7.3.18 23 / 34
7.3.17 23 / 34
7.3.16 23 / 34
7.3.15 23 / 34
7.3.14 23 / 34
7.3.13 23 / 34
7.3.12 23 / 34
7.3.11 23 / 34
7.3.10 23 / 34
7.3.9 23 / 34
7.3.8 23 / 34
7.3.7 23 / 34
7.3.6 23 / 34
7.3.5 23 / 34
7.3.4 23 / 34
7.3.3 23 / 34
7.3.2 23 / 34
7.3.1 23 / 34
7.3.0 23 / 34
7.2.6 23 / 34
7.2.5 23 / 34

v9.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.21

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (kaminobot) were replaced by new maintainers (kaminoadmin). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: kaminobot → GitHub Actions (on 2026-03-19) provenance

This version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.20

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (kaminobot) were replaced by new maintainers (kaminoadmin). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: kaminobot → GitHub Actions (on 2026-02-25) provenance

This version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.19

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (kaminobot) were replaced by new maintainers (kaminoadmin). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: kaminobot → GitHub Actions (on 2026-02-19) provenance

This version was published by a different npm account than previous versions on 2026-02-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.18

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (kaminobot) were replaced by new maintainers (kaminoadmin). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: kaminobot → GitHub Actions (on 2026-01-30) provenance

This version was published by a different npm account than previous versions on 2026-01-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.17

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (kaminobot) were replaced by new maintainers (kaminoadmin). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: kaminobot → GitHub Actions (on 2026-01-21) provenance

This version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.16

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (kaminobot) were replaced by new maintainers (kaminoadmin). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: kaminobot → GitHub Actions (on 2026-01-21) provenance

This version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.2.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.2.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.