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

tornadus/ez80ai

https://github.com/tornadus/ez80ai · scanned 2026-06-16 00:40 UTC (2 months, 1 week ago)

70 raw signals (0 security + 70 graph)

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

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 52 actionable findings from 1 signal source. 18 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
82.9
/100
Security checks
83
0 findings
System graph
83
66.7% cov · 52 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 0 Medium 5 Low 36 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 52 Crowd 0 Layer: Software 29 Frontend 1 Security 1 Cicd 1 Quality 20
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 82.9/100 with 66.7% coverage. It contains 456 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 70 findings — concentrated in quality (38), software (29), frontend (1). Risk profile is low: 0 critical, 0 high, 5 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 41 of 52 actionable findings. 70 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — ez80research/evaluate.py:189
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
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 cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 152 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 Tests conf 1.00 Low test-to-source ratio
3 tests / 19 src (ratio 0.16).
low System graph quality Integrity conf 1.00 19 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: libez80.py:ld_hl_nn, libez80.py:ld_hl_n 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.
19 occurrences
repo-level (19 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `from_legacy` in loadmodel.py:19
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 quality Integrity conf 1.00 Old/deprecated-named symbol `from_legacy` in modelspec.py:195
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: di
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:174
low System graph software Dead code conf 1.00 Possibly dead Python function: ei
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:175
low System graph software Dead code conf 1.00 Possibly dead Python function: fixup_word_16
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:129
low System graph software Dead code conf 1.00 Possibly dead Python function: halt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:173
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_a_bc
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:289
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_b_c
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:303
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_b_e
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:304
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_b_h
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:305
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_bc_label
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:246
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_bc_mem_label
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:277
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_c_l
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:307
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_d_h
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:309
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_d_n
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:255
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_e_c
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:311
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_e_l
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:312
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_e_n
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:256
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_hl_n
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:259
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_ix_nn
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:239
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_iy_nn
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:240
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_l_c
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:316
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_l_d
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:317
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_l_e
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:318
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_l_n
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:258
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_mem_label_bc
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:276
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_mem_label_de
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:275
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_mem_label_sp
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:279
low System graph software Dead code conf 1.00 Possibly dead Python function: ld_sp_mem_label
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:280
low System graph software Dead code conf 1.00 Possibly dead Python function: nop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:168
low System graph software Dead code conf 1.00 Possibly dead Python function: rst
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
libez80.py:172
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph quality Complexity conf 1.00 Very large file: buildchat84.py (2280 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/f041a1de-5497-4cee-a913-279035fb779b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f041a1de-5497-4cee-a913-279035fb779b/

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.