CodeInspectus
NPM · CODEINSPECTUS · SCANNED AUG 3
Local-first MCP security scanner and CLI for AI-generated applications.
Available components
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 Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (101 of 105), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (101 of 105), so this covers what we could see, not the whole tree. 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 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1099 tokens (~183/item across 6 items; 6 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
npm · codeinspectus
claude mcp add synvoya-codeinspectus -- npx -y codeinspectus
codex mcp add synvoya-codeinspectus -- npx -y codeinspectus
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"synvoya-codeinspectus": {
"type": "local",
"command": [
"npx",
"-y",
"codeinspectus"
],
"enabled": true
}
}
} openclaw mcp add synvoya-codeinspectus --command npx --arg -y --arg codeinspectus
mcp_servers:
synvoya-codeinspectus:
command: "npx"
args: ["-y", "codeinspectus"] {
"mcpServers": {
"synvoya-codeinspectus": {
"command": "npx",
"args": [
"-y",
"codeinspectus"
]
}
}
} 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +53
- Install scripts: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Maintenance: pass → unverified ▼ functional
- License: pass → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.23 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −30
- Stability: 0.17 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 +37
- 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 0
- Security disclosure: unverified → fail ▼ functional
- Package version: 1.5.0 → 2.0.0 functional
- 29 Jul 26 −53
- Known CVEs: partial → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- License: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Licence: MIT functional
- Package version: 1.0.0 → 1.5.0 functional
- 28 Jul 26 +53
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Tool coverage: 83 functional
- First check of Schema quality: fail functional
- Licence: MIT functional
- 27 Jul 26 6
First indexed and scored.
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 npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 101 packages
101 packages in the resolved dependency tree · 100 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
codeinspectus_compliance_report Code-level compliance coverage report ~141
Produce a per-framework code-level control-coverage view for a prior scan (NIST CSF 2.0, ISO 27001:2022, SOC 2, CIS v8.1, Essential Eight, OWASP Web/LLM). Reports 'X of N code-visible controls have findings' with the code-visible subset as the explicit denominator. This is NOT a compliance audit, certification, or attestation — code-level evidence only.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | — | Restrict the report to one framework. Default: all frameworks. |
| scan_id | string | yes | scan_id returned by a prior codeinspectus_scan call. |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | string | yes | — |
| frameworks | array | yes | — |
| posture_note | string | yes | — |
| posture_score | number | yes | — |
| scan_id | string | yes | — |
No examples provided.
codeinspectus_explain_finding Explain a finding in depth ~85
Return a deep explanation and full remediation plan for a single finding id from a prior scan: what the weakness is, why it matters, concrete fix steps, and references.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | The finding id (e.g. CI-0007) to explain in depth. |
| scan_id | string | yes | scan_id the finding belongs to. |
| Name | Type | Req | Description |
|---|---|---|---|
| explanation | string | yes | — |
| finding | object | yes | — |
| references | array | yes | — |
| remediation | — | yes | — |
| why_it_matters | string | yes | — |
No examples provided.
codeinspectus_generate_sbom Generate a software bill of materials ~133
Generate a CycloneDX or SPDX SBOM for the target project using Trivy plus the first-party offline Pub lockfile inventory, with native Pub fallback when Trivy is unavailable. Writes the SBOM file to the chosen output path and returns its location and component count. Offline.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | — | SBOM format (default: cyclonedx). |
| output_path | string | — | Where to write the SBOM file. Default: ~/.codeinspectus/sbom/<project>.<fmt>.json. |
| path | string | yes | Absolute path to the project to generate an SBOM for. |
| Name | Type | Req | Description |
|---|---|---|---|
| component_count | integer | yes | — |
| coverage_state | string | yes | — |
| ecosystems | array | yes | — |
| format | string | yes | — |
| generated | boolean | yes | — |
| limitations | array | yes | — |
| lockfiles_analyzed | integer | yes | — |
| note | string | — | — |
| offline | boolean | yes | — |
| output_path | string | yes | — |
| providers | array | yes | — |
No examples provided.
codeinspectus_list_rules List active rules and detector versions ~79
List the active detectors and engine versions, the CodeInspectus detection-database version and date, Trivy vulnerability-DB freshness, bundled Pub advisory-database provenance/freshness, and the custom CodeInspectus AI-code rules and native detector packs currently shipped.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | — | Filter to one engine's rules/detectors. |
| Name | Type | Req | Description |
|---|---|---|---|
| advisory_databases | array | yes | — |
| custom_rule_count | integer | yes | — |
| custom_rules | array | yes | — |
| detection_db_date | string | yes | — |
| detection_db_version | string | yes | — |
| engine_setup | object | yes | — |
| engines | array | yes | — |
| native_packs | array | yes | — |
| note | string | yes | — |
| trivy_db_date | string | — | — |
No examples provided.
codeinspectus_rescan Re-scan and diff against a prior scan ~144
Re-run a scan after fixes were applied and diff against a prior scan_id (or the most recent scan of the same path). Reports which findings are resolved, which remain, and which were newly introduced, plus fresh technology and native-pack execution coverage. Use this to verify fixes. Never writes to your code or repo.
| Name | Type | Req | Description |
|---|---|---|---|
| max_findings | integer | — | — |
| path | string | yes | Absolute path to the repository or directory to rescan. |
| prior_scan_id | string | — | scan_id of a previous scan to diff against. Defaults to the most recent scan of this path. |
| scanners | array | — | — |
| severity_threshold | string | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| dependency_coverage | array | — | — |
| detected_technologies | array | yes | — |
| disclaimer | string | yes | — |
| introduced | array | yes | — |
| not_rechecked | array | yes | — |
| not_rechecked_note | string | — | — |
| pack_coverage | array | yes | — |
| partial | boolean | yes | — |
| prior_scan_id | string | yes | — |
| remaining | array | yes | — |
| resolved | array | yes | — |
| scan_id | string | yes | — |
| summary | object | yes | — |
| target | string | yes | — |
No examples provided.
codeinspectus_scan Scan code for security issues ~253
Run a full local security scan of a path: bundled engines (Opengrep SAST, Gitleaks secrets, Trivy SCA/IaC/license), CodeInspectus's offline native Pub SCA, plus AI-code-specific checks (client-side secret exposure, Supabase RLS/inverted-auth, prompt-injection sinks, API-boundary failures, and explicit runtime-control misconfiguration). Returns CWE-keyed findings with fix recommendations, detected repository technologies, explicit native-pack execution counts, compliance tags, and three-state repository evidence for supported runtime controls. Fully offline — zero network egress at scan time. Never writes to your code or repo.
| Name | Type | Req | Description |
|---|---|---|---|
| include_compliance | boolean | — | Include the per-framework compliance overview in the result (default: true). |
| max_findings | integer | — | Cap the number of findings returned to protect agent context (default: 200). |
| path | string | yes | Absolute path to the repository or directory to scan. |
| scanners | array | — | Limit which scanner classes run: sast, secret, vuln, misconfig, license, ai. Default: all. |
| severity_threshold | string | — | Only return findings at or above this severity (default: info — all). |
| Name | Type | Req | Description |
|---|---|---|---|
| compliance_overview | object | — | — |
| component_signatures | object | — | — |
| dependency_coverage | array | — | — |
| detected_technologies | array | yes | — |
| disclaimer | string | yes | — |
| duration_ms | integer | yes | — |
| engine_details | array | yes | — |
| engine_setup | object | — | — |
| engines_run | array | yes | — |
| findings | array | yes | — |
| git_safety | object | yes | — |
| git_scope | object | — | — |
| history_revision | object | — | — |
| offline | boolean | yes | — |
| pack_coverage | array | yes | — |
| repository_root | string | — | — |
| scan_config | object | — | — |
| scan_id | string | yes | — |
| secret_coverage | string | — | — |
| secret_suppression | object | — | — |
| security_control_evidence | array | — | — |
| started_at | string | yes | — |
| summary | object | yes | — |
| target | string | yes | — |
| total_findings_before_limit | integer | yes | — |
| trivy_db_date | string | — | — |
| trivy_db_provenance | object | — | — |
| truncated | boolean | yes | — |
| warnings | array | yes | — |
No examples provided.