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.

decodedcorp/decoded

https://github.com/decodedcorp/decoded · scanned 2026-06-17 01:55 UTC (1 month, 1 week ago)

532 raw signals (0 security + 532 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 84 Medium 172 Low 135 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 500 Crowd 0 Layer: Software 26 Frontend 156 Network 2 Hardware 4 Security 44 Cicd 3 Quality 188 Api 77

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

3 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 6 places

View all duplicates & near-duplicates findings →

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 `isLegacy` in packages/web/lib/components/PostBadge…

View all legacy markers findings →

Commented-out code 25 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 packages/ai-server/src/editorial_article/ig_c…
info Commented-code block (6 lines) in packages/ai-server/src/services/raw_posts/sch…
info Commented-code block (5 lines) in packages/ai-server/src/services/raw_posts/pro…
info Commented-code block (12 lines) in packages/ai-server/src/services/raw_posts/pr…
info Commented-code block (6 lines) in packages/ai-server/src/services/raw_posts/pro…
info Commented-code block (5 lines) in packages/ai-server/src/services/raw_posts/pro…
info Commented-code block (5 lines) in packages/ai-server/src/services/editorial_art…
info Commented-code block (5 lines) in packages/ai-server/src/config/_container.py:4…
info Commented-code block (10 lines) in packages/web/app/admin/login/page.tsx:12
info Commented-code block (6 lines) in packages/web/app/admin/raw-posts/page.tsx:243
info Commented-code block (5 lines) in packages/web/lib/api/posts.ts:44
info Commented-code block (6 lines) in packages/web/lib/api/admin/raw-posts.ts:115

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

low Stray `console.log` in TS/JS — .claude/skills/gstack/scripts/host-config-export…
medium Insecure pattern 'node_child_process' in .claude/skills/gstack/scripts/host-con… .claude/skills/gstack/scripts/host-config-export.…:18
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: .claude/agents/supabase-query-bui… .claude/agents/supabase-query-builder.md:29
high Agent instruction/config may expose a secret: .claude/skills/gstack/docs/design… .claude/skills/gstack/docs/designs/SLATE_HOST.md:290
high Agent instruction/config may expose a secret: .claude/skills/gstack/docs/design… .claude/skills/gstack/docs/designs/SIDEBAR_MESSAG…:126
info Commented-code block (5 lines) in packages/ai-server/src/config/_container.py:4…
low Old/deprecated-named symbol `model_copy` in packages/ai-server/src/config/helpe…

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/8391d6a0-ffee-4621-aaa9-aced9eb9dc01/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8391d6a0-ffee-4621-aaa9-aced9eb9dc01/

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.