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.

pyreon/pyreon

https://github.com/pyreon/pyreon · scanned 2026-06-15 23:43 UTC (2 months, 4 weeks ago)

1452 raw signals (0 security + 1452 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 4 weeks ago · v1 · 1449 actionable findings from 1 signal source. 3 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 1449 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 71 Medium 159 Low 394 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1449 Crowd 0 Layer: Frontend 261 Network 8 Hardware 4 Security 69 Cicd 2 Quality 1031 Api 74

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.

Legacy markers 2 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

2 matching findings on this repo

low Stray `console.log` in TS/JS — scripts/check-no-legacy-playground.ts:112
low Old/deprecated-named symbol `nLegacy` in scripts/check-no-legacy-playground.ts:…

View all legacy markers findings →

Commented-out code 817 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 (6 lines) in playwright.config.ts:81
info Commented-code block (5 lines) in docs/vite.config.ts:15
info Commented-code block (5 lines) in docs/src/sidebar-config.ts:4
info Commented-code block (5 lines) in docs/src/env.d.ts:3
info Commented-code block (8 lines) in docs/src/entry-client.ts:19
info Commented-code block (7 lines) in docs/src/components/Toc.tsx:16
info Commented-code block (5 lines) in docs/src/components/PageMeta.tsx:9
info Commented-code block (6 lines) in docs/src/components/PyreonLanding.tsx:6
info Commented-code block (7 lines) in docs/src/components/Header.tsx:44
info Commented-code block (7 lines) in docs/src/routes/_layout.tsx:35
info Commented-code block (5 lines) in docs/src/routes/docs/[...slug].tsx:3
info Commented-code block (5 lines) in docs/src/examples/ui-core/theme-mode-provider…

View all commented-out code findings →

Config drift 49 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 Stray `console.log` in TS/JS — packages/tools/lint/src/config/loader.ts:21
medium `dangerouslySetInnerHTML` used in a React component — packages/core/runtime-dom…
low Node manifest has dependencies but no lockfile: packages/internals/playwright-c… packages/internals/playwright-config/package.json
low Node manifest has dependencies but no lockfile: packages/internals/vitest-confi… packages/internals/vitest-config/package.json
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: .claude/plans/native-platforms-ph… .claude/plans/native-platforms-phase1-roadmap.md:73
high Agent instruction/config may expose a secret: .claude/plans/native-platforms-pl… .claude/plans/native-platforms-platform-abstracti…:286
high Agent instruction/config may expose a secret: .claude/plans/native-platforms-to… .claude/plans/native-platforms-todomvc-walkthroug…:24
info Commented-code block (6 lines) in playwright.config.ts:81
info Commented-code block (5 lines) in docs/vite.config.ts:15
info Commented-code block (5 lines) in docs/src/sidebar-config.ts:4
info Commented-code block (10 lines) in packages/zero/zero/src/tests/vite-plugin-con…

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/80f9f934-8db6-4082-bf71-886df2b37fd3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/80f9f934-8db6-4082-bf71-886df2b37fd3/

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.