io.github.ciloops/vuln-check
Local vulnerability scan on top of grype, with prioritised upgrade actions for agents.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
@ciloops/vuln-checkclaude mcp add vuln-check -- npx -y @ciloops/vuln-check@0.1.3 mcp
{
"mcpServers": {
"vuln-check": {
"command": "npx",
"args": [
"-y",
"@ciloops/vuln-check@0.1.3",
"mcp"
]
}
}
}
ghcr.io/ciloops/vuln-check:0.1.3claude mcp add vuln-check -- docker run -i --rm ghcr.io/ciloops/vuln-check:0.1.3 mcp
{
"mcpServers": {
"vuln-check": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/ciloops/vuln-check:0.1.3",
"mcp"
]
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
vuln-check
Vulnerability truth for AI agents. Runs grype locally, merges an OSV freshness overlay, and returns a prioritised answer with concrete upgrade targets instead of a 40 KB JSON dump.
- Any language with a lockfile (npm, PyPI, Go, Maven, Cargo, RubyGems, Composer, NuGet, Hex, Pub, Swift, R, Conan…), OS packages, container images, SBOMs.
- One score per finding: CVSS + EPSS + CISA KEV + fix availability.
- Remediation plan per package: smallest version that closes every finding,
breakingflag. CLEANis ~20 tokens. Nothing runs on a server; nothing leaves your machine except the optional OSV query.
Install
# grype is required
brew install grype # or: curl -sSfL https://get.anchore.io/grype | sh -s -- -b /usr/local/bin
go install github.com/ciloops/vuln-check/cmd/vuln-check@latest
# or
brew install ciloops/tap/vuln-check # macOS cask
# or
npx @ciloops/vuln-check scan .
Binaries for Linux/macOS/Windows on the Releases page. Docker: ghcr.io/ciloops/vuln-check (bundles grype).
CLI
vuln-check scan . # agent format, OSV overlay on
vuln-check scan python:3.12-slim # image, pulled from the registry
vuln-check scan sbom:bom.cdx.json
vuln-check scan --format sarif --sarif-out out.sarif .
vuln-check scan --fail-above 69 --no-osv . # CI gate, exit 2 above threshold
vuln-check vuln CVE-2024-3094
vuln-check db update
Output (--format agent):
{"status":"ACTION_REQUIRED","target":"dir:.","packages":412,"findings":17,"shown":5,"sources":["grype","osv"],
"actions":[{"package":"pkg:npm/minimist","current":"1.2.5","target":"1.2.6","breaking":false,"fixes":["CVE-2021-44906"],"score":59}],
"top":[{"id":"CVE-2021-44906","package":"minimist@1.2.5","severity":"CRITICAL","score":59,"epss":0.015,"fixed_in":["1.2.6"]}],
"unfixable":3}
status: CLEAN | REVIEW (all findings < 40) | ACTION_REQUIRED. fresh: true marks advisories that came from OSV before grype-db ingested them. unfixable counts findings with no fix on the current release line.
MCP
Tools: scan_dir, scan_image, scan_sbom, vuln_lookup, db_update.
Claude Code:
claude mcp add vuln-check -- vuln-check mcp
# or the plugin (adds a skill that tells Claude when to scan):
claude plugin marketplace add ciloops/vuln-check && claude plugin install vuln-check
Cursor / Windsurf / VS Code (.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, .vscode/mcp.json):
{ "mcpServers": { "vuln-check": { "command": "vuln-check", "args": ["mcp"] } } }
Codex (~/.codex/config.toml):
[mcp_servers.vuln-check]
command = "vuln-check"
args = ["mcp"]
Add --no-osv to the args to keep the dependency list off the network.
GitHub Action
- uses: ciloops/vuln-check@v1
with:
target: . # or an image ref
fail-above: 69
sarif: vuln.sarif
- uses: github/codeql-action/upload-sarif@v3
if: always()
with: { sarif_file: vuln.sarif }
Score
severity = CVSS base × 6 (label fallback) · exploit = EPSS × 30 · KEV: +10, floor 85 · no fix: × 0.85. Clamped to 0–100. See internal/score.
Freshness
grype-db builds daily and grype refreshes it at most every 2 h. The OSV overlay queries api.osv.dev with the purls grype inventoried (language ecosystems only) and adds anything grype-db has not seen yet, usually minutes after a GHSA is published. Disable with --no-osv.
Limits
- No lockfile → transitive dependencies are invisible. Same as every scanner.
- Remediation plans assume a linear release line per package; direct vs transitive is not distinguished yet.
- Version comparison is a generic tokenizer, not per-ecosystem parsers. Good enough for "smallest fix above current"; edge cases exist (PEP 440 post-releases, exotic Maven qualifiers).
Development
go test ./...
go build ./cmd/vuln-check
Tests run against a fake grype (cmd/vuln-check/testdata/fake-grype.sh) and fixtures in internal/grype/testdata. CI runs a real grype e2e.
Release: tag vX.Y.Z → goreleaser publishes binaries, checksums, ghcr image, Homebrew cask for macOS (needs HOMEBREW_TAP_GITHUB_TOKEN and the ciloops/homebrew-tap repo) and the npm package via trusted publishing (OIDC, no token: configure the GitHub Actions trusted publisher for @ciloops/vuln-check on npmjs.com, workflow release.yml).
License
Apache-2.0. grype and syft are Apache-2.0 by Anchore. Vulnerability data: NVD (public domain), GHSA (CC-BY 4.0), OSV (per source), CISA KEV, FIRST EPSS.
Questions fréquentes
Qu'est-ce que io.github.ciloops/vuln-check ?
Local vulnerability scan on top of grype, with prioritised upgrade actions for agents.
Comment installer io.github.ciloops/vuln-check ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add vuln-check -- npx -y @ciloops/vuln-check@0.1.3 mcp. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.ciloops/vuln-check ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
io.github.ciloops/vuln-check est-il open source ?
Oui. Son code est sur GitHub sous licence Apache-2.0.
Qui maintient io.github.ciloops/vuln-check ?
Il est publié par ciloops. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.