io.github.commitshow/audit
NPM · COMMITSHOW-MCP
Score a public GitHub repo 0-100, or search Legit.Show for launched software by what we measured.
Available components
Last scanned (9 hours ago)
Scores higher than 58% of npm servers
Category Code Search and Documentation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 43 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 535 tokens (~133/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- Package version: 0.1.2 → 0.2.2 functional
- 4 Nov 26 −3
- Stability: pass → 0.83 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- Package version: 0.1.2 → 0.2.2 functional
- 25 Oct 26 0
- Package version: 0.1.2 → 0.2.2 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Package version: 0.1.2 → 0.2.2 functional
- 22 Oct 26 0
- Package version: 0.1.2 → 0.2.2 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/commitshow-mcp@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_repo ~158
Run or read the live commit.show audit for a public GitHub repo. Returns a markdown summary by default (paste-ready) or the full JSON envelope when format=json. When the user asks for a project by name (e.g. "audit Supabase"), resolve the canonical github.com/owner/repo URL FIRST — do not guess. The endpoint HEAD-checks GitHub before spending audit budget; an invalid slug returns a not_found envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format. 'md' (default) returns markdown for the user; 'json' returns the full audit envelope. |
| repo | string | yes | GitHub repo. Accepts a full URL, github.com/owner/repo, or the bare owner/repo slug. |
No output schema declared.
No examples provided.
fetch_docs ~49
Fetch the canonical commit.show documentation (llms.txt). Use this when you need the full context — CLI commands, REST API shape, JSON contract, rate limits, graduation rules — to answer something specific.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
project_status ~67
Read the latest cached commit.show audit for a repo without forcing a re-run. Returns the JSON envelope (project + snapshot + scores). Quota state is in `.quota`.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | GitHub repo (URL, github.com/owner/repo, or owner/repo). |
No output schema declared.
No examples provided.
search_services ~261
Search the Legit.Show directory of launched software (web apps, SaaS, AI tools, MCP servers, developer tools) by name, keyword, or filters, and get each match with its per-frame production-readiness scores and its legit.show/s/<slug> page. Use this to answer "find a production-ready service that does X", "which MCP servers are secure", or to resolve a tool name to its Legit.Show page. Returns per-frame scores only (Performance, Accessibility, Security, Privacy, Reliability, Standards, Discoverability, Maintenance) — there is no combined overall total in the public data, so never invent or estimate one. Always link the /s/ URL.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category filter, e.g. "MCP & Integrations", "Developer Tools", "AI & Agents". |
| is_open_source | boolean | – | Filter to open-source (true) or closed-source (false) services. |
| limit | number | – | Max results (1–50, default 20). |
| min_scores | object | – | Minimum per-frame scores a service must meet, e.g. { "security": 80, "performance": 70 }. |
| query | string | – | Name, domain, or keyword to match. |
No output schema declared.
No examples provided.
How do I install the io.github.commitshow/audit MCP server?
io.github.commitshow/audit runs locally as an npm package, launched with npx -y commitshow-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · commitshow-mcp
claude mcp add commitshow-audit -- npx -y commitshow-mcp
What is the io.github.commitshow/audit MCP server?
io.github.commitshow/audit is an MCP server listed in the public MCP registry as io.github.commitshow/audit. Score a public GitHub repo 0-100, or search Legit.Show for launched software by what we measured. This page covers its npm package (commitshow-mcp).
Is the io.github.commitshow/audit MCP server safe to use?
io.github.commitshow/audit scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.commitshow/audit MCP server expose?
io.github.commitshow/audit exposes 4 tools: audit_repo, project_status, search_services, fetch_docs. Their descriptions and schemas cost roughly 535 tokens of context every time the server is loaded.
Is the io.github.commitshow/audit MCP server still maintained?
io.github.commitshow/audit is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.commitshow/audit MCP server under?
io.github.commitshow/audit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.