← Home

@suvijya/kevin

npm

AI-powered dev assistant & cybersecurity agent

6
Versions
MIT
License
Yes
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

suvijya

Keywords

aicliassistantcybersecuritydev-tools

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:postinstall AI (install-scripts): Postinstall is a pure echo banner with no network or code execution; stable pattern for this CLI package. ai

Versions (showing 6 of 6)

Version Deps Published
1.1.6 0 / 0
1.1.1 0 / 0
1.1.0 0 / 0
1.0.4 0 / 0
1.0.3 0 / 0
1.0.2 0 / 0

v1.1.6

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: echo " 🚀 KEVIN v1.1.6 INSTALLED SUCCESSFULLY! To initialize your secure scanning environment, please run: kevin sandbox build Happy Hacking! 🛡️ "

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.

v1.1.1

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: echo " 🚀 KEVIN v1.1.1 INSTALLED SUCCESSFULLY! To initialize your secure scanning environment, please run: kevin sandbox build Happy Hacking! 🛡️ "

LOW No provenance attestation provenance

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

v1.1.0

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.

v1.0.4

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.

v1.0.3

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.

v1.0.2

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.