BintzGavin/helios

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.

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

Scan timing: clone 9.22s · analysis 38.48s · 16.9 MB · GitHub API rate-limit (preflight)

https://github.com/BintzGavin/helios · scanned 2026-06-05 14:29 UTC (5 days, 5 hours ago) · 10 languages

849 raw signals (191 security + 658 graph) 51st percentile · Typescript · medium (20-100K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 5 hours ago · v2 · 463 actionable findings from 2 signal sources. 57 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 · 328 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	52.0	0.25	13.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	67.0	0.15	10.05
`practices_score`	67.0	0.15	10.05
`code_quality`	70.0	0.10	7.00
Overall		1.00	69.1

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 62 Medium 78 Low 263 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 135 System graph 328 Crowd 0 Layer: Quality 69 Software 160 Cicd 2 Frontend 182 Api 50

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 30 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/`.

12 matching findings on this repo

info Commented-code block (9 lines) in packages/player/src/index.ts:2212
info Commented-code block (5 lines) in packages/player/src/sandbox.test.ts:66
info Commented-code block (6 lines) in packages/player/src/features/text-tracks.test…
info Commented-code block (5 lines) in packages/player/src/features/audio-fader.test…
info Commented-code block (8 lines) in packages/renderer/tests/verify-audio-loop.ts:…
info Commented-code block (7 lines) in packages/renderer/tests/verify-seek-driver-of…
info Commented-code block (5 lines) in packages/renderer/tests/verify-dom-media-attr…
info Commented-code block (5 lines) in packages/renderer/tests/verify-audio-playback…
info Commented-code block (7 lines) in packages/renderer/tests/verify-smart-audio-fa…
info Commented-code block (12 lines) in packages/renderer/tests/verify-video-loop.ts…
info Commented-code block (7 lines) in packages/renderer/tests/verify-smart-codec-pr…
info Commented-code block (8 lines) in packages/renderer/tests/verify-enhanced-dom-p…

View all commented-out code findings →

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

12 matching findings on this repo

low File has no detected symbols: vite.config.js
low File has no detected symbols: tailwind.config.js
low File has no detected symbols: postcss.config.js
low File has no detected symbols: packages/player/vite.config.ts
low File has no detected symbols: packages/player/vitest.config.ts
low Stray `console.log` in TS/JS — vite.build-example.config.js:17
low Stray `console.log` in TS/JS — packages/renderer/tests/verify-browser-config.ts…
info TODO/FIXME marker in shipping code — packages/cli/src/utils/config.ts:36
high Dangling fetch: POST https://api.cloudflare.com/client/v4/accounts/${this.confi…
high Dangling fetch: POST https://api.machines.dev/v1/apps/${this.config.appName}/ma…
high Dangling fetch: DELETE https://api.machines.dev/v1/apps/${this.config.appName}/…
high Dangling fetch: GET https://api.machines.dev/v1/apps/${this.config.appName}/mac…

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/111cca79-b1fd-4658-bc93-2073688e83a6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/111cca79-b1fd-4658-bc93-2073688e83a6/

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.