input-sanitizer vs CodeInspectus
input-sanitizer is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
input-sanitizer is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. CodeInspectus is an MCP server published by Synvoya. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  CodeInspectus | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.3.1 Downloads/month (npm): 931 Downloads/week (npm): 101 Forks (GitHub): 10 Stars (GitHub): 49 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | input-sanitizerno longer listed · | CodeInspectus |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 49 |
| Forks (GitHub) (differs) | 0 | 10 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | On your machine (codeinspectus) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/synvoya/codeinspectus |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of input-sanitizer
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Input validation, sanitization, and security expert
-
Semgrep catches security vulnerabilities in real-time and guides Claude to write secure code from the start.
-
Security review for Claude-generated code. Pattern-based warnings on edits, LLM-powered diff review on Stop, and an agentic commit reviewer that catches injection, XSS, SSRF…
-
PreToolUse security reminder hook for Claude Code. Catches 12 common security anti-patterns in Edit/Write/MultiEdit operations BEFORE they happen — command injection (exec…
-
Comprehensive application security toolbox for Claude Code. 62 skills across 8 frameworks (OWASP Top 10, OWASP API Top 10, STRIDE, PASTA, LINDDUN, MITRE ATT&CK, SANS/CWE Top 25…
-
Security scanning and vulnerability auditing following OWASP Top 10 guidelines with automated remediation
What each says it does
input-sanitizer
Scan code for missing input validation and generate sanitizers
CodeInspectus
Local-first MCP security scanner and CLI for AI-generated applications.
How to run each
input-sanitizer
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
CodeInspectus As a local MCP server: npm package
claude mcp add --transport stdio codeinspectus -- npx -y codeinspectusCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: input-sanitizer · What it can do: CodeInspectus · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.