io.github.neogeweb3/code-health-suite

PYPI · CODE-HEALTH-SUITE · SCANNED AUG 3

16 engines, 28 MCP tools for Python code quality. Zero external dependencies.

Available components

−23 this week 21 21 Trust /100

Trust breakdown (6 categories)

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 →

Supply Chain Security50

Malware scan not yet available for this package.Unverified
No known CVEs affecting this package version or its production dependencies.Pass
Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
No production dependencies, so there is no dependency health to assess. View diagnostics → Pass

Provenance & Transparency32

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
License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
Actively maintained (last published 136 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability0

Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified

Stability & Change Management0

Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified

Tool Coverage0

Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified

Capabilities0

Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

pypi · code-health-suite

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add neogeweb3-code-health-suite -- uvx code-health-suite

# add to Codex CLI

codex mcp add neogeweb3-code-health-suite -- uvx code-health-suite

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "neogeweb3-code-health-suite": {
      "type": "local",
      "command": [
        "uvx",
        "code-health-suite"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add neogeweb3-code-health-suite --command uvx --arg code-health-suite

# ~/.hermes/config.yaml

mcp_servers:
  neogeweb3-code-health-suite:
    command: "uvx"
    args: ["code-health-suite"]

// mcp.json

{
  "mcpServers": {
    "neogeweb3-code-health-suite": {
      "command": "uvx",
      "args": [
        "code-health-suite"
      ]
    }
  }
}

Changelog

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.

3 Aug 26 −15
- Malware scan: pass → unverified ▼ security
2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
31 Jul 26 −5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
27 Jul 26 0
- Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
- Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
26 Jul 26 44

First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional

Show 3 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Analysed pypi/[email protected]

Provenance none

Ecosystem: pypi · Outcome: none

Install scripts 1 script

Hook	Tier	Command
build_backend	allowlisted	`hatchling.build`

Dependencies 0 packages

0 packages in the resolved dependency tree.

MCP tools — 28 exposed · ~2,159 tokens

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.

Tool Tokens

analyze_change_impact ~99

Analyze the ripple effect of changing specific files. Shows direct dependents, transitive impact, affected tests, and an impact score (fraction of project affected). Use before refactoring to understand blast radius.

Input Output Examples

Name	Type	Req	Description
changed_files	array	yes	List of file paths (relative to root) that are being changed.
max_depth	integer	—	Max transitive dependency depth (default: 10).
path	string	yes	Project root directory.

No output schema declared.

No examples provided.

analyze_complexity ~109

Analyze Python code complexity for a file or directory. Returns per-function metrics: cyclomatic complexity (McCabe), cognitive complexity, nesting depth, function length, and letter grades (A-F).

Input Output Examples

Name	Type	Req	Description
path	string	yes	File or directory path to analyze.
sort_by	string	—	Sort metric (default: complexity).
threshold	integer	—	Cyclomatic complexity threshold (default: 10).
top	integer	—	Return only top N functions by complexity. 0 = all.

No output schema declared.

No examples provided.

analyze_coupling ~63

Analyze module coupling metrics: afferent coupling (Ca), efferent coupling (Ce), instability (Ce/(Ca+Ce)), and hub scores. Identifies tightly-coupled modules that may resist change.

Input Output Examples

Name	Type	Req	Description
path	string	yes	Project root directory.

No output schema declared.

No examples provided.

analyze_imports ~55

Analyze Python import dependency graph. Returns module metrics, circular dependencies (cycles), orphan modules, hub modules, and instability scores. Use to understand project architecture.

Input Output Examples

Name	Type	Req	Description
path	string	yes	Root directory of the Python project to analyze.

No output schema declared.

No examples provided.

analyze_test_quality ~80

Analyze test suite quality: assertion density, test length, naming conventions, magic numbers, and more. Returns per-file and per-test metrics with a quality score (0-100) and grade.

Input Output Examples

Name	Type	Req	Description
max_length	integer	—	Max test function length before flagging (default: 50).
path	string	yes	Root directory containing test files.

No output schema declared.

No examples provided.

analyze_type_coverage ~54

Analyze Python type annotation coverage: function signatures, parameters, return types, Any usage, and type: ignore comments. Returns per-file metrics and coverage percentages.

Input Output Examples

Name	Type	Req	Description
path	string	yes	File or directory path to analyze.

No output schema declared.

No examples provided.

audit_dependencies ~63

Audit Python project dependencies for outdated packages and known vulnerabilities. Reads requirements.txt and/or pyproject.toml. Returns per-dependency status, latest versions, and CVE/vulnerability details.

Input Output Examples

Name	Type	Req	Description
path	string	yes	Project root directory containing requirements.txt or pyproject.toml.

No output schema declared.

No examples provided.

audit_docstrings ~62

Audit Python docstring coverage and quality. Checks public functions, methods, classes, and modules for missing or low-quality docstrings. Returns per-entity coverage, missing docstrings, and quality issues.

Input Output Examples

Name	Type	Req	Description
path	string	yes	File or directory path to audit.

No output schema declared.

No examples provided.

audit_env_vars ~59

Audit environment variable usage: find undefined vars referenced in code, unused vars in .env files, secrets in templates, and missing .env.example entries. Supports Python, JavaScript, and shell scripts.

Input Output Examples

Name	Type	Req	Description
path	string	yes	Project root directory.

No output schema declared.

No examples provided.

audit_git_commits ~153

Audit recent git commits in a repository. Extracts changed files and runs static analysis (security scan, complexity) on each commit. Returns per-commit grades, security findings, and complexity violations.

Input Output Examples

Name	Type	Req	Description
author	string	—	Filter commits by author name.
commits	integer	—	Number of recent commits to audit (default: 10).
repo	string	yes	Path to the git repository to audit.
severity	string	—	Minimum security finding severity (default: low).
since	string	—	Audit commits since date (e.g., '3 days ago', '2026-03-01').
threshold	integer	—	Complexity threshold for flagging functions (default: 10).

No output schema declared.

No examples provided.

check_naming ~66

Check Python naming conventions (PEP 8). Detects violations: functions/methods must be snake_case, classes must be CamelCase, constants must be UPPER_SNAKE_CASE. Returns violations with suggestions.

Input Output Examples

Name	Type	Req	Description
path	string	yes	File or directory path to check.

No output schema declared.

No examples provided.

detect_bugs ~154

Detect common Python semantic bugs using AST analysis. Finds 8 categories: missing f-strings, mutable class variables, late-binding closures, call-expression defaults (datetime.now()), mutable default arguments, assert-on-tuple, unreachable code, and unreachable exception handlers. Every finding indicates a likely real bug, not a style violation.

Input Output Examples

Name	Type	Req	Description
min_severity	string	—	Minimum severity to report (default: info).
path	string	yes	File or directory path to scan.
rules	array	—	Filter by specific rules. Options: missing-fstring, mutable-class-var, late-binding-closure, call-default, mutable-default-arg, assert-tuple, unreachable-code, unreachable-except. Omit for all rules.

No output schema declared.

No examples provided.

find_clones ~114

Detect code clones (duplicated code blocks) in a Python project. Finds Type-1 (exact), Type-2 (renamed), and Type-3 (near-miss) clones. Returns clone pairs with similarity scores and cluster analysis.

Input Output Examples

Name	Type	Req	Description
min_lines	integer	—	Minimum function length to consider (default: 5).
path	string	yes	Directory path to scan for clones.
threshold	number	—	Similarity threshold 0.0-1.0 (default: 0.8).

No output schema declared.

No examples provided.

find_dead_code ~77

Detect unused imports, functions, variables, and arguments in Python code. Supports cross-module analysis to reduce false positives.

Input Output Examples

Name	Type	Req	Description
category	string	—	Filter by category. Omit for all categories.
min_severity	string	—	Minimum severity level (default: info).
path	string	yes	File or directory path to scan.

No output schema declared.

No examples provided.

find_hotspots ~106

Find code hotspots — files with high git churn AND high complexity. These are the riskiest files in a project: frequently changed AND hard to understand. Requires a git repository. Returns hotspot scores, risk levels, and churn/complexity breakdown.

Input Output Examples

Name	Type	Req	Description
path	string	yes	Git repository root path.
since_days	integer	—	Look back N days for churn data (default: 180).
top	integer	—	Return top N hotspots (default: 20).

No output schema declared.

No examples provided.

full_health_check ~105

Run all analyses (complexity + dead code + security + imports + clones + test quality + type coverage + env audit + naming + TODO debt + bug detection + docstring coverage) on a Python project and return a combined health report with scores, grades, and top issues. Note: hotspot, dependency, and change impact require additional context (git repo, requirements files, changed files) so are excluded from this scan.

Input Output Examples

Name	Type	Req	Description
path	string	yes	Directory path to analyze.

No output schema declared.

No examples provided.

get_bug_score ~64

Get a bug detection health score (0-100) with grade (A-F), bug profile classification (clean/fstring_heavy/closure_heavy/etc.), and breakdown by rule and severity. Quick bug health check.

Input Output Examples

Name	Type	Req	Description
path	string	yes	Directory path to scan.

No output schema declared.

No examples provided.

get_complexity_score ~52

Get an overall complexity health score (0-100) with letter grade (A-F), complexity profile classification, and top offenders. Quick project health check.

Input Output Examples

Name	Type	Req	Description
path	string	yes	Directory path to analyze.

No output schema declared.

No examples provided.

get_docstring_score ~57

Get a docstring coverage health score (0-100) with grade. Measures what percentage of public entities have docstrings and penalizes low-quality docstrings. Shows worst files.

Input Output Examples

Name	Type	Req	Description
path	string	yes	Directory path to audit.

No output schema declared.

No examples provided.

get_git_audit_score ~69

Get a quick overall grade and score for recent commits in a repo. Returns the aggregate score, grade, commit count, and security summary.

Input Output Examples

Name	Type	Req	Description
commits	integer	—	Number of recent commits to audit (default: 10).
repo	string	yes	Path to the git repository.

No output schema declared.

No examples provided.

get_hotspot_score ~53

Get overall hotspot health score (0-100) with grade. Measures concentration of risk (churn x complexity). Lower scores indicate more hotspots that need attention.

Input Output Examples

Name	Type	Req	Description
path	string	yes	Git repository root path.

No output schema declared.

No examples provided.

get_import_health ~54

Get an import graph health score (0-100) with grade. Penalizes circular dependencies, orphan modules, unstable modules, and hub concentration. Quick architecture health check.

Input Output Examples

Name	Type	Req	Description
path	string	yes	Root directory to analyze.

No output schema declared.

No examples provided.

get_naming_score ~59

Get a naming convention health score (0-100) with grade. Measures PEP 8 naming compliance: snake_case functions, CamelCase classes, UPPER_SNAKE_CASE constants.

Input Output Examples

Name	Type	Req	Description
path	string	yes	Directory path to check.

No output schema declared.

No examples provided.

get_security_score ~46

Get an overall security health score (0-100) with grade, profile, and top vulnerability rules. Quick security posture assessment.

Input Output Examples

Name	Type	Req	Description
path	string	yes	Directory path to scan.

No output schema declared.

No examples provided.

get_todo_score ~52

Get a technical debt health score (0-100) with grade based on density and severity of TODO/FIXME/HACK markers. Shows hotspot files.

Input Output Examples

Name	Type	Req	Description
path	string	yes	Directory path to scan.

No output schema declared.

No examples provided.

get_type_score ~49

Get overall type coverage health score (0-100) with grade. Measures annotation completeness, Any usage, and type: ignore density.

Input Output Examples

Name	Type	Req	Description
path	string	yes	File or directory path to analyze.

No output schema declared.

No examples provided.

scan_todos ~128

Scan source code for technical debt markers: TODO, FIXME, HACK, XXX, BUG, NOTE, OPTIMIZE, REFACTOR comments. Returns items with file, line, tag, severity, and message. Optionally enriches with git blame metadata.

Input Output Examples

Name	Type	Req	Description
blame	boolean	—	Enrich with git blame metadata (author, date). Slower.
path	string	yes	File or directory path to scan.
severity	string	—	Filter by minimum severity level.
tag	string	—	Filter by specific tag (e.g., TODO, FIXME, HACK).

No output schema declared.

No examples provided.

security_scan ~57

Scan Python code for security vulnerabilities: command injection, SQL injection, path traversal, hardcoded secrets, unsafe deserialization, XSS, and more. Maps findings to CWE identifiers.

Input Output Examples

Name	Type	Req	Description
path	string	yes	File or directory path to scan.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	44
27 Jul	44
28 Jul	44
30 Jul	26
31 Jul	21
1 Aug	21
2 Aug	36
3 Aug	21