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.
Sign up free Scan another repo

777genius/agent-teams-ai

https://github.com/777genius/agent-teams-ai · scanned 2026-05-15 23:20 UTC (2 weeks, 6 days ago) · 10 languages

402 findings (33 legacy + 369 scanner) 19th percentile · Typescript · huge (>500K LoC) Scanner says 51 (higher by 25)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 6 days ago · v1 · 29 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
65.9
/100
Repobility
81
29 legacy
9-layer
51
100.0% cov · 0 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-17-v4 calibration-aware
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 82.3 0.25 20.57
testing_score 95.0 0.20 19.00
documentation_score 59.8 0.15 8.97
practices_score 65.0 0.15 9.75
code_quality 46.6 0.10 4.66
Overall 1.00 75.7
Calibrated penalty buckets (security_score): web: 3.0 · agent: 5.6 · docker: 5.8 · journey: 3.3
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 20 Medium 7 Low 2 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 29 9-layer 0 Crowd 0 Layer: Quality 23 Cicd 5 Security 1

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 23 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 Public web service has no security.txt .well-known/security.txt
  • medium Public web app has no Content Security Policy index.html
  • medium [ERR002] Empty Catch Block: Empty catch blocks hide errors. src/renderer/components/team/TeamListView.tsx:760
  • medium [ERR002] Empty Catch Block: Empty catch blocks hide errors. src/renderer/components/team/TeamDetailView.tsx:2642
  • medium localStorage write failures are swallowed silently src/features/recent-projects/renderer/utils/recen…:107
  • medium Codex session log reader may expose prompts or tool-call content src/features/recent-projects/main/adapters/output…:17
  • medium Codex session log reader may expose prompts or tool-call content src/features/member-log-stream/core/domain/polici…:183
  • medium localStorage write failures are swallowed silently src/features/agent-graph/renderer/hooks/useGraphS…:30
  • medium Agent auto-approve or skip-permissions mode is easy to enable docs/research/best-abstraction-for-electron.md:105
  • medium Duplicated implementation block across source files src/features/member-work-sync/main/infrastructure…:1
  • medium Duplicated implementation block across source files src/features/member-work-sync/main/adapters/outpu…:28
  • medium Duplicated implementation block across source files src/features/member-log-stream/main/adapters/outp…:171
View all fragile runtime 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/8736580a-0a1e-4ba0-a1a8-b26a3ba33ed6/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8736580a-0a1e-4ba0-a1a8-b26a3ba33ed6/

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.