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.

steph-frtech/aidos

https://github.com/steph-frtech/aidos · scanned 2026-06-16 00:23 UTC (2 months, 2 weeks ago)

610 raw signals (0 security + 610 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 581 actionable findings from 1 signal source. 29 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 1 finding
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.
1 matching finding on this repo
  • low Near-duplicate function bodies in 2 places repo-level
View all duplicates & near-duplicates findings →
Legacy markers 2 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.
2 matching findings on this repo
  • low Old/deprecated-named symbol `replayModeLegacy` in front/web/components/AgentsPa…
  • low Old/deprecated-named symbol `replayModeLegacy` in front/web/app/agents/page.tsx…
View all legacy markers findings →
Commented-out code 147 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 playwright.config.ts:3
  • info Commented-code block (6 lines) in tests/e2e/v2-deploy.spec.ts:142
  • info Commented-code block (8 lines) in tests/e2e/v3.spec.ts:369
  • info Commented-code block (10 lines) in tests/e2e/agents.spec.ts:288
  • info Commented-code block (6 lines) in front/web/components/SchedulerSection.tsx:8
  • info Commented-code block (5 lines) in front/web/components/AgentsPanel.tsx:96
  • info Commented-code block (7 lines) in front/web/components/GovernancePanel.tsx:30
  • info Commented-code block (8 lines) in front/web/components/ErasurePanel.tsx:15
  • info Commented-code block (5 lines) in front/web/components/CompoundingSection.tsx:3
  • info Commented-code block (7 lines) in front/web/app/governance/page.tsx:6
  • info Commented-code block (5 lines) in front/web/app/global-invariants/page.tsx:6
  • info Commented-code block (5 lines) in front/web/app/sensors/page.tsx:4
View all commented-out code findings →
Config drift 123 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
  • high Agent instruction/config may expose a secret: .claude/agent-memory/step-verifie… .claude/agent-memory/step-verifier/project_fk11_a…:12
  • high Agent instruction/config may expose a secret: .claude/agent-memory/step-verifie… .claude/agent-memory/step-verifier/MEMORY.md:165
  • high Agent instruction/config may expose a secret: .claude/marketplaces/superpowers/… .claude/marketplaces/superpowers/skills/writing-s…:1063
  • high Agent instruction/config may expose a secret: .claude/marketplaces/cdesign-expo… .claude/marketplaces/cdesign-expo/.claude/skills/…:28
  • high Agent instruction/config may expose a secret: .claude/marketplaces/cdesign-expo… .claude/marketplaces/cdesign-expo/.claude/marketp…:1063
  • high Agent instruction/config may expose a secret: .claude/marketplaces/cdesign-expo… .claude/marketplaces/cdesign-expo/.claude/marketp…:247
  • high Agent instruction/config may expose a secret: .claude/marketplaces/cdesign-expo… .claude/marketplaces/cdesign-expo/.claude/marketp…:92
  • high Agent instruction/config may expose a secret: .claude/marketplaces/cdesign-expo… .claude/marketplaces/cdesign-expo/.claude/marketp…:163
  • high Agent instruction/config may expose a secret: .claude/marketplaces/cdesign-expo… .claude/marketplaces/cdesign-expo/.claude/marketp…:215
  • high Agent instruction/config may expose a secret: .claude/marketplaces/cdesign-expo… .claude/marketplaces/cdesign-expo/.claude/marketp…:328
  • high Agent instruction/config may expose a secret: .claude/marketplaces/cdesign-expo… .claude/marketplaces/cdesign-expo/.claude/marketp…:362
  • high Agent instruction/config may expose a secret: .claude/marketplaces/cdesign-expo… .claude/marketplaces/cdesign-expo/.claude/marketp…:186
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/425306ce-bafc-4444-8b37-764eea98080d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/425306ce-bafc-4444-8b37-764eea98080d/

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.