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.

TortoiseWolfe/eightysix

https://github.com/TortoiseWolfe/eightysix · scanned 2026-06-16 00:41 UTC (2 months, 1 week ago)

346 raw signals (6 security + 340 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 303 actionable findings from 2 signal sources. 46 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 · 298 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 10 High 12 Medium 64 Low 123 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 5 System graph 298 Crowd 0 Layer: Quality 136 Cicd 6 Software 11 Frontend 111 Hardware 2 Security 28 Api 9

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.

Duplicates & near-duplicates 2 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

2 matching findings on this repo

low Near-duplicate function bodies in 3 places
low Near-duplicate function bodies in 2 places

View all duplicates & near-duplicates findings →

Commented-out code 85 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 (5 lines) in playwright.config.ts:140
info Commented-code block (6 lines) in tests/integration/auth/oauth-flow.test.ts:101
info Commented-code block (8 lines) in tests/integration/auth/sign-in-flow.test.ts:1…
info Commented-code block (5 lines) in tests/contract/admin/admin-access.contract.te…
info Commented-code block (7 lines) in tests/e2e/mobile-dropdown-screenshot.spec.ts:…
info Commented-code block (5 lines) in tests/e2e/game-3d.spec.ts:22
info Commented-code block (5 lines) in tests/e2e/color-contrast.spec.ts:5
info Commented-code block (5 lines) in tests/e2e/embed-theme-contrast.spec.ts:5
info Commented-code block (7 lines) in tests/e2e/auth.setup.ts:75
info Commented-code block (5 lines) in tests/e2e/security/payment-isolation.spec.ts:…
info Commented-code block (5 lines) in tests/e2e/tests/accessibility.spec.ts:208
info Commented-code block (5 lines) in tests/e2e/tests/mobile-orientation.spec.ts:153

View all commented-out code findings →

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

9 matching findings on this repo

low Stray `console.log` in TS/JS — scripts/generate-author-config.js:40
low Stray `console.log` in TS/JS — scripts/supabase/set-auth-config.ts:53
medium Insecure pattern 'node_child_process' in next.config.ts:2 next.config.ts:2
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: CLAUDE.md CLAUDE.md:275
high Agent instruction/config may expose a secret: .claude/knowledge/docker/nodejs_r… .claude/knowledge/docker/nodejs_rocks_in_docker_d…:6
info Commented-code block (5 lines) in playwright.config.ts:140
high Dangling fetch: GET https://api.supabase.com/v1/projects/${projectRef}/config/a…
high Dangling fetch: PATCH https://api.supabase.com/v1/projects/${projectRef}/config…

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/e25b1bd4-a492-49d9-a252-1b04024b4829/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e25b1bd4-a492-49d9-a252-1b04024b4829/

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.