tailuge/billiards

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.

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

Scan timing: clone 5.64s · analysis 24.56s · 1.2 MB · GitHub preflight 447ms

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

245 raw signals (65 security + 180 graph) 68th percentile · Typescript · medium (20-100K LoC) System graph score 88 (lower by 12)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 83 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	55.0	0.25	13.75
`testing_score`	100.0	0.20	20.00
`documentation_score`	61.0	0.15	9.15
`practices_score`	70.0	0.15	10.50
`code_quality`	78.2	0.10	7.82
Overall		1.00	76.2

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 15 Medium 16 Low 79 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 45 System graph 83 Crowd 0 Layer: Software 78 Quality 18 Security 3 Cicd 3 Api 1 Frontend 25

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.

Commented-out code 4 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/`.

4 matching findings on this repo

info Commented-code block (10 lines) in test/rules/snooker.spec.ts:611
info Commented-code block (5 lines) in test/network/bot/aimcalculator.spec.ts:31
info Commented-code block (8 lines) in test/model/physics.spec.ts:168
info Commented-code block (5 lines) in src/model/physics/stronge.ts:44

View all commented-out code findings →

Config drift 2 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.

2 matching findings on this repo

low File has no detected symbols: webpack.config.js
low File has no detected symbols: test/jest.config.js

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/351d1050-179e-4361-b6c1-7e841150551e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/351d1050-179e-4361-b6c1-7e841150551e/

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.