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.

danny-exnodes/LAAM

https://github.com/danny-exnodes/LAAM · scanned 2026-06-17 01:53 UTC (1 month, 1 week ago)

168 raw signals (0 security + 168 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -9.7 (diff) · 166 actionable findings from 1 signal source. 2 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 · 166 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 25 Low 18 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 166 Crowd 0 Layer: Api 1 Frontend 28 Hardware 1 Security 8 Quality 128

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 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `laam_legacy` in src/app/api/ingest/route.test.ts:79

View all legacy markers findings →

Commented-out code 102 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 next.config.ts:4
info Commented-code block (8 lines) in src/auth.config.ts:4
info Commented-code block (7 lines) in src/app/globals-contrast.test.ts:1
info Commented-code block (5 lines) in src/app/api/pdf/route.ts:4
info Commented-code block (5 lines) in src/app/api/chat/route.ts:102
info Commented-code block (6 lines) in src/app/api/chat/route.test.ts:340
info Commented-code block (8 lines) in src/app/api/users/[id]/route.ts:9
info Commented-code block (5 lines) in src/app/api/access-tokens/route.ts:18
info Commented-code block (6 lines) in src/app/api/access-tokens/[id]/route.ts:7
info Commented-code block (6 lines) in src/app/api/ingest/route.ts:12
info Commented-code block (5 lines) in src/app/api/ingest/route.test.ts:95
info Commented-code block (5 lines) in src/app/api/connectors/[id]/[action]/route.ts…

View all commented-out code findings →

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

3 matching findings on this repo

info Commented-code block (7 lines) in next.config.ts:4
info Commented-code block (8 lines) in src/auth.config.ts:4
info Commented-code block (5 lines) in src/components/workflows/editor/NodeConfigPan…

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/be7a0947-40c3-4eae-9621-fb57f7d77611/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/be7a0947-40c3-4eae-9621-fb57f7d77611/

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.