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.
58 of your 110 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 2.72s · analysis 9.44s · 2.8 MB · GitHub API rate-limit (preflight)

bdfinst/agentic-dev-team

https://github.com/bdfinst/agentic-dev-team · scanned 2026-06-05 13:07 UTC (5 days, 9 hours ago) · 10 languages

346 raw signals (104 security + 242 graph) 11th percentile · Typescript · small (2-20K LoC)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 9 hours ago · v2 · 189 actionable findings from 2 signal sources. 36 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 23.3 0.25 5.83
testing_score 46.0 0.20 9.20
documentation_score 89.0 0.15 13.35
practices_score 65.0 0.15 9.75
code_quality 63.4 0.10 6.34
Overall 1.00 50.5
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 `searchUsersLegacy` in evals/fixtures/te-duplicate-…
  • low Old/deprecated-named symbol `processInvoiceLegacy` in evals/fixtures/te-long-fu…
View all legacy markers findings →
Commented-out code 5 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/`.
5 matching findings on this repo
  • info Commented-code block (6 lines) in evals/comparative/score.py:231
  • info Commented-code block (7 lines) in evals/fixtures/test-missing-edge-cases.test.t…
  • info Commented-code block (10 lines) in evals/fixtures/te-duplicate-code.ts:22
  • info Commented-code block (14 lines) in evals/fixtures/te-long-functions.ts:44
  • info Commented-code block (6 lines) in evals/fixtures/sds-duplicate-with-canonical/p…
View all commented-out code 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/0b85a2c0-d147-40cd-a902-26cae92c4136/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0b85a2c0-d147-40cd-a902-26cae92c4136/

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.