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.

steveantini/legalos

https://github.com/steveantini/legalos · scanned 2026-06-16 00:22 UTC (2 months, 2 weeks ago)

100 raw signals (0 security + 100 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 100 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 100 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 6 Medium 14 Low 11 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 100 Crowd 0 Layer: Api 1 Frontend 21 Security 7 Cicd 1 Quality 70

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 51 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 (7 lines) in proxy.ts:98
info Commented-code block (5 lines) in next.config.ts:52
info Commented-code block (6 lines) in docs/design/aperture/tweaks-panel.jsx:12
info Commented-code block (6 lines) in docs/design/aperture/design-canvas.jsx:2
info Commented-code block (6 lines) in components/workspace/department-launchpad-con…
info Commented-code block (5 lines) in components/workspace/workspace-rail.tsx:101
info Commented-code block (5 lines) in components/workspace/collapsible-rail-group.t…
info Commented-code block (8 lines) in components/workspace/agent-card.tsx:116
info Commented-code block (7 lines) in components/workspace/agent-details-panel.tsx:…
info Commented-code block (7 lines) in components/workspace/home/home-greeting.tsx:14
info Commented-code block (5 lines) in components/chat/message-list.tsx:152
info Commented-code block (5 lines) in components/chat/chat-interface.tsx:164

View all commented-out code findings →

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

8 matching findings on this repo

medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: .claude/skills/database-security.… .claude/skills/database-security.md:224
high Agent instruction/config may expose a secret: .claude/skills/nextjs.md .claude/skills/nextjs.md:355
high Agent instruction/config may expose a secret: .claude/skills/api-security.md .claude/skills/api-security.md:33
high Agent instruction/config may expose a secret: .claude/skills/environment-manage… .claude/skills/environment-management.md:63
high Agent instruction/config may expose a secret: .claude/skills/infra-security.md .claude/skills/infra-security.md:33
high Agent instruction/config may expose a secret: .claude/skills/supabase.md .claude/skills/supabase.md:123
info Commented-code block (5 lines) in next.config.ts:52

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/a81ee9d5-07f1-4827-a536-c4107cf26ba9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a81ee9d5-07f1-4827-a536-c4107cf26ba9/

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.