sibidharan/zealphp

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.

39 of your 111 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 4.66s · analysis 7.28s · 10.5 MB · GitHub API rate-limit (preflight)

https://github.com/sibidharan/zealphp · scanned 2026-06-05 15:05 UTC (5 days, 2 hours ago) · 10 languages

202 raw signals (100 security + 102 graph) 57th percentile · Php · large (100-500K LoC) System graph score 76 (lower by 4)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 2 hours ago · v2 · 93 actionable findings from 2 signal sources. 58 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 46 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	65.0	0.15	9.75
`security_score`	44.3	0.25	11.07
`testing_score`	85.0	0.20	17.00
`documentation_score`	97.8	0.15	14.67
`practices_score`	91.0	0.15	13.65
`code_quality`	56.5	0.10	5.65
Overall		1.00	71.8

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 22 Medium 15 Low 24 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 47 System graph 46 Crowd 0 Layer: Quality 47 Cicd 9 Security 5 Software 10 Frontend 3 Network 3 Hardware 1 Api 15

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 1 finding

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 2 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

2 matching findings on this repo

medium `fetch()` without try/.catch or AbortSignal — public/js/pages/legacy-apps.js:63
high Dangling fetch: POST /api/convert (public/js/pages/legacy-apps.js:63)

View all legacy markers findings →

Commented-out code 6 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

6 matching findings on this repo

info Commented-code block (8 lines) in bench/tail/tail_bench.py:220
info Commented-code block (10 lines) in public/js/site-nav.js:140
info Commented-code block (5 lines) in public/js/demo-shell.js:8
info Commented-code block (5 lines) in public/js/learn-demo-viewers.js:104
info Commented-code block (8 lines) in public/js/learn-tictactoe.js:1
info Commented-code block (8 lines) in labs-bench/tail_bench.py:220

View all commented-out code findings →

Config drift 1 finding

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

1 matching finding on this repo

low Very large file: examples/agents/config_converter.py (2976 lines)

View all config drift findings →

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/e4dc0a0f-1ff8-4e8d-be22-c8d2e5e3c6a1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e4dc0a0f-1ff8-4e8d-be22-c8d2e5e3c6a1/

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.