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
20 of your 35 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 37.26s for a 71.9 MB repo slow.
  • Repobility's analysis ran in 1.2s after the clone landed.

phpstan/phpstan

https://github.com/phpstan/phpstan · scanned 2026-06-05 17:55 UTC (4 days, 21 hours ago) · 10 languages

146 raw signals (34 security + 112 graph) 11/13 scanners ran 57th percentile · Php · small (2-20K LoC) System graph score 82 (lower by 10)

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

Complete repo analysis

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

JSON
Combined
76.1
/100
Security checks
71
16 findings
System graph
82
100.0% cov · 51 findings
Critical
1
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 100.0 0.25 25.00
testing_score 45.0 0.20 9.00
documentation_score 71.0 0.15 10.65
practices_score 89.0 0.15 13.35
code_quality 80.0 0.10 8.00
Overall 1.00 72.0
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 3 Medium 3 Low 39 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 16 System graph 51 Crowd 0 Layer: Cicd 5 Security 3 Quality 23 Software 34 Api 1 Frontend 1

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.

Commented-out code 10 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/`.
10 matching findings on this repo
  • info Commented-code block (8 lines) in website/.eleventy.js:16
  • info Commented-code block (5 lines) in website/infra/functions/phpstan-org-edge.js:13
  • info Commented-code block (6 lines) in website/infra/lib/website-stack.ts:29
  • info Commented-code block (5 lines) in website/src/js/MainMenuViewModel.ts:7
  • info Commented-code block (5 lines) in website/src/js/codeMirror.ts:52
  • info Commented-code block (5 lines) in website/src/js/phpantom/lspClient.ts:7
  • info Commented-code block (5 lines) in website/src/js/phpantom/worker.ts:10
  • info Commented-code block (7 lines) in website/src/js/editor/goToDefinition.ts:5
  • info Commented-code block (7 lines) in website/src/js/editor/occurrences.ts:12
  • info Commented-code block (7 lines) in website/src/js/editor/docBlock.ts:18
View all commented-out code findings →
Config drift 6 findings
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.
6 matching findings on this repo
  • low File has no detected symbols: website/vite.config.js
  • low File has no detected symbols: website/tailwind.config.js
  • low File has no detected symbols: website/postcss.config.js
  • low File has no detected symbols: website/functional-tests/playwright.config.ts
  • low File has no detected symbols: website/visual-tests/playwright.config.ts
  • low File has no detected symbols: website/infra/vitest.config.ts
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/924284a5-1e6c-401f-9514-6eb4afdc4125/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/924284a5-1e6c-401f-9514-6eb4afdc4125/

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.