pardnchiu/Agenvoy

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.

Scan timing: clone 6.43s · analysis 3.92s · 6.7 MB · GitHub preflight 392ms

https://github.com/pardnchiu/Agenvoy · scanned 2026-05-31 01:22 UTC (5 days, 8 hours ago) · 10 languages

137 findings (119 legacy + 18 scanner) 11th percentile · Go · medium (20-100K LoC) Scanner says 89 (lower by 27)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 8 hours ago · v2 · last Δ +0.1 (diff) · 128 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	87.9	0.25	21.98
`testing_score`	25.0	0.20	5.00
`documentation_score`	74.7	0.15	11.21
`practices_score`	42.0	0.15	6.30
`code_quality`	48.2	0.10	4.82
Overall		1.00	62.1

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 84 Medium 7 Low 19 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 119 9-layer 9 Crowd 0 Layer: Security 10 Quality 101 Software 14 Api 1 Frontend 1 Cicd 1

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.

Fragile runtime 97 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

12 matching findings on this repo

medium [COMP001] High cognitive complexity: Function `_iter_source_files` has cognitiv… extensions/skills/code-reviewer/scripts/analyze_j…:95
medium [COMP001] High cognitive complexity: Function `_parse_go_mod` has cognitive com… extensions/skills/code-reviewer/scripts/analyze_g…:51
medium [SEC091] Go: net/http server without timeouts: HTTP server without ReadHeaderTi… internal/agents/provider/openaiCodex/login.go:183
medium [SEC091] Go: net/http server without timeouts: HTTP server without ReadHeaderTi… cmd/app/cmdDeamon.go:258
medium Bare except continues silently extensions/skills/tool-reviewer/scripts/scan_tool…:517
medium Bare except continues silently extensions/skills/tool-reviewer/scripts/scan_tool…:280
medium Bare except continues silently extensions/skills/tool-reviewer/scripts/scan_tool…:251
medium Bare except continues silently extensions/skills/skill-creator/scripts/package_s…:109
medium Bare except continues silently extensions/skills/skill-creator/scripts/init_skil…:300
medium Bare except continues silently extensions/skills/skill-creator/scripts/init_skil…:292
medium Bare except continues silently extensions/skills/skill-creator/scripts/init_skil…:280
medium Public web service has no security.txt .well-known/security.txt

View all fragile runtime 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 Legacy-named symbol `meta_copy` in extensions/skills/tool-reviewer/scripts/scan…

View all legacy markers findings →

Config drift 1 finding

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.

1 matching finding on this repo

medium No CI/CD configuration found

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/1ff33bf4-f2fc-4a9a-bdbf-25c857b0ef2b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1ff33bf4-f2fc-4a9a-bdbf-25c857b0ef2b/

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.