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.
Sign up free Scan another repo

mattzirkelbach-pixel/zeke-status

https://github.com/mattzirkelbach-pixel/zeke-status · scanned 2026-06-16 04:32 UTC (1 month, 4 weeks ago)

16 raw signals (0 security + 16 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
89.3
/100
Security checks
89
0 findings
System graph
89
66.7% cov · 16 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 1 Medium 6 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 16 Crowd 0 Layer: Software 3 Security 5 Quality 8
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 89.3/100 with 66.7% coverage. It contains 72 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 16 findings — concentrated in quality (8), security (5), software (3). Risk profile is high: 0 critical, 1 high, 6 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in build-status.py:40
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
build-status.py:40 Subprocess shell true
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in mc-server.py:74
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
mc-server.py:74 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in index.html:432
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
index.html:432 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in mc-index.html:235
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
mc-index.html:235 Direct innerhtml assignment
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 6 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 6 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: build-status.py:sf, zeke-diagnostic.py:sf This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Docs conf 1.00 No README detected
No README file was found. Generated repos without README context are hard to operate, validate, or safely hand off.
ReadmeRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `words_old` in quality-scorer.py:102
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: file_exists
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mc-server.py:141
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mc-server.py:245
low System graph software Dead code conf 1.00 Possibly dead Python function: run_cmd
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
zeke-diagnostic.py:12
low System graph quality Integrity conf 1.00 Stub function `log_message` (body is just `pass`/`return`) — mc-server.py:245
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
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/e6095fa8-1fd3-447a-aa6a-73719b29891f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e6095fa8-1fd3-447a-aa6a-73719b29891f/

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.