io.github.goldmembrane/codesafer
NPM · CLEANER-CODE
Scans AI-generated code for invisible Unicode, Trojan Source, and supply-chain threats.
Available components
Last scanned (17 hours ago)
Scores higher than 75% of npm servers
Category Security
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 36 of 106 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 (ISC).Pass
- Actively maintained (last published 223 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 322 tokens (~53/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Stability: pass → 0.97 functional
- 15 Nov 26 0
- Stability: 0.97 → pass security
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −5
- Stability: pass → 0.63 functional
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 21 Nov 2026 · Analysed npm/cleaner-code@1.0.1
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 →
Dependencies 106 packages
| Packages resolved | 106 |
|---|---|
| Stale | 36 |
| 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 →
ai_analyze ~69
Deep AI analysis of code using the trained CodeBERT model. Classifies code chunks as malicious or benign with confidence scores. Detects obfuscated payloads, novel attack patterns, and threats that static rules may miss.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the file to analyze with AI |
No output schema declared.
No examples provided.
check_dependencies ~38
Check package.json for typosquatting, suspicious install scripts, and dependency risks
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to package.json file |
No output schema declared.
No examples provided.
explain_finding ~41
Get detailed explanation of a specific threat category including attack scenarios, real-world examples, and remediation steps
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | The threat category to explain |
No output schema declared.
No examples provided.
scan_directory ~66
Recursively scan a directory for hidden malicious code patterns across all source files
| Name | Type | Req | Description |
|---|---|---|---|
| dir_path | string | yes | Absolute path to the directory to scan |
| extensions | array | – | File extensions to scan (e.g., [".js", ".ts"]). Defaults to common source file extensions. |
No output schema declared.
No examples provided.
scan_file ~54
Scan a single file for hidden malicious code patterns (invisible chars, BiDi, homoglyphs, steganography, obfuscation, etc.)
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Absolute path to the file to scan |
No output schema declared.
No examples provided.
scan_rules_file ~54
Scan an AI configuration/rules file for prompt injection and Rules File Backdoor attacks
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the AI rules file (e.g., .cursorrules, CLAUDE.md) |
No output schema declared.
No examples provided.
How do I install the io.github.goldmembrane/codesafer MCP server?
io.github.goldmembrane/codesafer runs locally as an npm package, launched with npx -y cleaner-code. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · cleaner-code
claude mcp add goldmembrane-codesafer -- npx -y cleaner-code
What is the io.github.goldmembrane/codesafer MCP server?
io.github.goldmembrane/codesafer is an MCP server listed in the public MCP registry as io.github.goldmembrane/codesafer. Scans AI-generated code for invisible Unicode, Trojan Source, and supply-chain threats. This page covers its npm package (cleaner-code).
Is the io.github.goldmembrane/codesafer MCP server safe to use?
io.github.goldmembrane/codesafer scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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.goldmembrane/codesafer MCP server expose?
io.github.goldmembrane/codesafer exposes 6 tools: scan_file, scan_directory, scan_rules_file, check_dependencies, ai_analyze, explain_finding. Their descriptions and schemas cost roughly 322 tokens of context every time the server is loaded.
Is the io.github.goldmembrane/codesafer MCP server still maintained?
io.github.goldmembrane/codesafer is still listed as active in the MCP registry. We last reached this channel on 21 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.goldmembrane/codesafer MCP server under?
io.github.goldmembrane/codesafer declares the ISC licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.goldmembrane/codesafer MCP server?
VerifyMCP ran 16 checks on io.github.goldmembrane/codesafer, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.