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.

davidesilver/ZeroHuman-Agency

https://github.com/davidesilver/ZeroHuman-Agency · scanned 2026-06-17 01:53 UTC (1 month, 1 week ago)

349 raw signals (0 security + 349 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 169 Medium 43 Low 98 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 334 Crowd 0 Layer: Software 21 Frontend 33 Hardware 6 Security 73 Cicd 2 Quality 41 Api 158

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 4 places repo-level
low Near-duplicate function bodies in 3 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 `_call_anthropic_direct_legacy` in python/src/conte…

View all legacy markers findings →

Commented-out code 3 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/`.

3 matching findings on this repo

info Commented-code block (8 lines) in src/app/layout.tsx:84
info Commented-code block (8 lines) in src/app/sitemap.ts:16
info Commented-code block (6 lines) in src/components/layout/brand-switcher.tsx:28

View all commented-out code findings →

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

12 matching findings on this repo

low Stray `console.log` in TS/JS — cli/src/commands/config.ts:10
medium Runtime service client appears to use placeholder configuration
high FastAPI POST `api_upsert_email_provider_config` without auth dependency — pytho… python/src/content_engine/api/routes.py:963
high FastAPI POST `create_agent_config` without auth dependency — python/src/content… python/src/content_engine/api/routes_agents.py:100
high FastAPI PUT `update_agent_config` without auth dependency — python/src/content_… python/src/content_engine/api/routes_agents.py:188
high FastAPI DELETE `delete_agent_config` without auth dependency — python/src/conte… python/src/content_engine/api/routes_agents.py:224
high Dangling fetch: POST /api/bootstrap/save-config (src/app/bootstrap/page.tsx:87)
high Dangling fetch: GET /api/system/config (src/app/(dashboard)/setup/page.tsx:145)
high Dangling fetch: GET /api/llm/providers/configured (src/app/(dashboard)/setup/pa…
high Dangling fetch: PATCH /api/system/config (src/app/(dashboard)/setup/page.tsx:63…
high Dangling fetch: GET /api/system/config (src/app/(dashboard)/settings/page.tsx:6…
high Dangling fetch: GET /api/v1/agent-configs (src/app/(dashboard)/settings/agenti/…

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/75e9483c-675f-4d61-9c27-767b33282700/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/75e9483c-675f-4d61-9c27-767b33282700/

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.