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

Scan timing: clone 2.45s · analysis 10.73s · 11.0 MB · GitHub API rate-limit (preflight)

duotify/GitHubClawToolkit

https://github.com/duotify/GitHubClawToolkit · scanned 2026-06-05 19:15 UTC (4 days, 17 hours ago) · 10 languages

382 raw signals (120 security + 262 graph) 9th percentile · Javascript · medium (20-100K LoC) System graph score 70 (lower by 28)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 17 hours ago · v2 · 91 actionable findings from 2 signal sources. 160 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 40.0 0.15 6.00
security_score 71.4 0.25 17.85
testing_score 20.0 0.20 4.00
documentation_score 39.0 0.15 5.85
practices_score 40.0 0.15 6.00
code_quality 18.1 0.10 1.81
Overall 1.00 41.5
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 1 finding
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/`.
1 matching finding on this repo
  • info Commented-code block (5 lines) in skills/skill-creator/scripts/improve_descript…
View all commented-out code findings →
Config drift 4 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.
4 matching findings on this repo
  • medium No CI/CD configuration found
  • low File has no detected symbols: workers/line-bot/test/config.test.js
  • low File has no detected symbols: workers/line-bot/src/config.js
  • low Old/deprecated-named symbol `bot_v2` in workers/line-bot/test/config.test.js:89
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/aa637b46-604e-402b-9db4-b6cca914c0e3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/aa637b46-604e-402b-9db4-b6cca914c0e3/

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.