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.
49 of your 118 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 4.76s · analysis 33.64s · 7.6 MB · GitHub API rate-limit (preflight)

chiriapp/chiri

https://github.com/chiriapp/chiri · scanned 2026-06-05 14:51 UTC (5 days, 4 hours ago) · 10 languages

320 raw signals (110 security + 210 graph) 44th percentile · Typescript · medium (20-100K LoC) System graph score 64 (higher by 4)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 52.0 0.25 13.00
testing_score 57.0 0.20 11.40
documentation_score 59.7 0.15 8.96
practices_score 100.0 0.15 15.00
code_quality 62.9 0.10 6.29
Overall 1.00 67.4
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 3 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/`.
3 matching findings on this repo
  • info Commented-code block (5 lines) in src/tests/lib/store/sync-orchestrator.test.ts…
  • info Commented-code block (6 lines) in src/lib/store/sync.ts:547
  • info Commented-code block (5 lines) in src/hooks/system/useFileDrop.ts:131
View all commented-out code findings →
Config drift 3 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.
3 matching findings on this repo
  • high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… src/utils/mobileconfig.ts:84
  • low File has no detected symbols: vite.config.ts
  • low File has no detected symbols: 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/6f3f00d5-217a-4552-abdf-9bb37630cb0a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6f3f00d5-217a-4552-abdf-9bb37630cb0a/

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.