Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

jirolao/ai-mission-control

https://github.com/jirolao/ai-mission-control · scanned 2026-06-16 04:29 UTC (2 months ago)

7 raw signals (0 security + 7 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months ago · v1 · 7 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

66.7% cov · 7 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 4 Low 2 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 7 Crowd 0 Layer: Frontend 1 Security 3 Quality 3

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 77.5/100 with 66.7% coverage. It contains 95 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 7 findings — concentrated in security (3), quality (3), frontend (1). Risk profile is low: 0 critical, 0 high, 4 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 6 of 7 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in index.html:178

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

index.html:178 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server.js:595

Found a known-risky pattern (node_child_process). Review and replace if possible.

server.js:595 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in telemetry.js:18

Found a known-risky pattern (node_child_process). Review and replace if possible.

telemetry.js:18 Node child process

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 7 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — server.js:586

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/368c3ef6-fdc1-4563-9862-b842b51dc4e9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/368c3ef6-fdc1-4563-9862-b842b51dc4e9/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.