Is Guardvibe safe and trustworthy?

tashan scores Guardvibe on public evidence — tashan score 55.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Guardvibe?

In Claude Code: run `claude mcp add guardvibe -- npx -y guardvibe`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

‹ The Index

Guardvibe

npm

Security infrastructure your AI can't be — deterministic, current past your model's training cutoff, whole-repo-aware, author-independent. Security MCP for vibe coding. 462 rules, 39 tools, CLI + doctor. Prompt-level shift-left security (secureprompt — e

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Work: Security review · Infrastructure and deployment

Who it is for: Security engineer · DevOps / SRE

Install (Claude Code):

claude mcp add guardvibe -- npx -y guardvibe

deep

“44 tools documented (check_code, check_project, scan_directory…); 9 worked examples; setup and auth covered; states a limit — “Security infrastructure your AI can't be”; read with 1 linked doc(s)”

This grade is wrong ›

tashan score: 55.0
Instruction depth: 94.0 (deep — documents every tool, with worked examples, setup and a stated limitation)
Adoption: 251/wk
Upkeep: 67.0
Freshness: 83.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: Apache-2.0

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 3.31.0 — this package, not its dependency tree

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

Signed build provenancepublished from public CI with an attestation

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Guardvibe scores 55 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-guardvibe.svg)](https://tashan.sh/capability/pkg-guardvibe.html)

npm ↗ · source ↗ · pkg:guardvibe

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?