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.

VerhexIO/deckent-develop

https://github.com/VerhexIO/deckent-develop · scanned 2026-06-16 00:49 UTC (2 months, 1 week ago)

658 raw signals (0 security + 658 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 638 actionable findings from 1 signal source. 20 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 · 638 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 7 Medium 134 Low 73 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 638 Crowd 0 Layer: Api 1 Frontend 35 Network 2 Hardware 2 Security 104 Cicd 3 Quality 491

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

3 matching findings on this repo

low Old/deprecated-named symbol `cleanOrphanIpcDirsLegacy` in tests/core/orphan-cle…
low Old/deprecated-named symbol `decisionsLegacy` in scripts/adr-validator.mjs:167
low Old/deprecated-named symbol `cleanOrphanIpcDirsLegacy` in src/core/orphan-clean…

View all legacy markers findings →

Commented-out code 410 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 (8 lines) in vitest.config.ts:8
info Commented-code block (8 lines) in tests/docker/timeout-with-work.test.ts:4
info Commented-code block (7 lines) in tests/docker/docker-hb.test.ts:4
info Commented-code block (5 lines) in tests/integration/provider-flow.test.ts:241
info Commented-code block (7 lines) in tests/integration/cascade-block-live.test.ts:7
info Commented-code block (6 lines) in tests/integration/prompt-quality-regression.t…
info Commented-code block (5 lines) in tests/config/nervous-faz1-smoke.test.ts:27
info Commented-code block (5 lines) in tests/monitor/alert-emitter.test.ts:99
info Commented-code block (7 lines) in tests/api/auth-bootstrap.test.ts:85
info Commented-code block (5 lines) in tests/api/directives-endpoint.test.ts:124
info Commented-code block (6 lines) in tests/api/process-endpoint.test.ts:14
info Commented-code block (5 lines) in tests/api/live-events.test.ts:12

View all commented-out code findings →

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

10 matching findings on this repo

low Very large file: tests/core/config.test.ts (1382 lines)
low Very large file: src/core/config.ts (2182 lines)
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: deckent-hub/skills/calendar-googl… deckent-hub/skills/calendar-google/SKILL.md:16
info Commented-code block (8 lines) in vitest.config.ts:8
info Commented-code block (5 lines) in tests/config/nervous-faz1-smoke.test.ts:27
info Commented-code block (6 lines) in tests/cli/config-nervous-i18n.test.ts:3
info Commented-code block (5 lines) in tests/orchestra/autonomous/engine-config-clon…
info Commented-code block (5 lines) in src/cli/commands/config-nervous.ts:3
info Commented-code block (7 lines) in src/core/config.ts:150

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/f6e30dfd-a9af-491e-9d57-51af25588472/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f6e30dfd-a9af-491e-9d57-51af25588472/

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.