CopilotKit/CopilotKit

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.

239 of your 478 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 8.85s · analysis 43.23s · 121.6 MB · GitHub API rate-limit (preflight)

https://github.com/CopilotKit/CopilotKit · scanned 2026-06-06 00:02 UTC (4 days, 3 hours ago) · 10 languages

6546 raw signals (438 security + 6108 graph) 10/13 scanners ran 37th percentile · Typescript · huge (>500K LoC) System graph score 52 (higher by 30)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 3 hours ago · v2 · 3044 actionable findings from 2 signal sources. 448 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 · 2911 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	78.0	0.20	15.60
`documentation_score`	95.0	0.15	14.25
`practices_score`	78.0	0.15	11.70
`code_quality`	61.0	0.10	6.10
Overall		1.00	81.6

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 244 Medium 213 Low 455 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 133 System graph 2911 Crowd 0 Layer: Software 62 Quality 2094 Security 89 Cicd 18 Frontend 548 Network 3 Hardware 54 Api 176

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 7 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.

7 matching findings on this repo

low Near-duplicate function bodies in 13 places repo-level
low Near-duplicate function bodies in 10 places repo-level
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 9 places
low Near-duplicate function bodies in 7 places

View all duplicates & near-duplicates findings →

Legacy markers 19 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.

12 matching findings on this repo

low Stray `console.log` in TS/JS — examples/v1/_legacy/copilot-openai-mongodb-atlas…
low Stray `console.log` in TS/JS — examples/v1/_legacy/saas-dynamic-dashboards/fron…
low Stray `console.log` in TS/JS — examples/v1/_legacy/saas-dynamic-dashboards/fron…
low Stray `console.log` in TS/JS — examples/v1/_legacy/saas-dynamic-dashboards/fron…
low Stray `console.log` in TS/JS — examples/v1/_legacy/saas-dynamic-dashboards/fron…
low Stray `console.log` in TS/JS — examples/v1/_legacy/saas-dynamic-dashboards/fron…
low Stray `console.log` in TS/JS — examples/v1/_legacy/saas-dynamic-dashboards/fron…
low Stray `console.log` in TS/JS — examples/v1/_legacy/saas-dynamic-dashboards/fron…
low Stray `console.log` in TS/JS — examples/v1/_legacy/saas-dynamic-dashboards/fron…
low Stray `console.log` in TS/JS — examples/v1/_legacy/saas-dynamic-dashboards/fron…
low Stray `console.log` in TS/JS — examples/v1/_legacy/saas-dynamic-dashboards/fron…
low Stray `console.log` in TS/JS — examples/v1/_legacy/saas-dynamic-dashboards/fron…

View all legacy markers findings →

Commented-out code 1822 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 (6 lines) in commitlint.config.js:3
info Commented-code block (7 lines) in showcase/integrations/claude-sdk-typescript/t…
info Commented-code block (7 lines) in showcase/integrations/claude-sdk-typescript/t…
info Commented-code block (7 lines) in showcase/integrations/claude-sdk-typescript/t…
info Commented-code block (7 lines) in showcase/integrations/claude-sdk-typescript/t…
info Commented-code block (5 lines) in showcase/integrations/claude-sdk-typescript/t…
info Commented-code block (11 lines) in showcase/integrations/claude-sdk-typescript/…
info Commented-code block (5 lines) in showcase/integrations/claude-sdk-typescript/t…
info Commented-code block (7 lines) in showcase/integrations/claude-sdk-typescript/t…
info Commented-code block (12 lines) in showcase/integrations/claude-sdk-typescript/…
info Commented-code block (7 lines) in showcase/integrations/claude-sdk-typescript/t…
info Commented-code block (5 lines) in showcase/integrations/claude-sdk-typescript/t…

View all commented-out code findings →

Config drift 63 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 [MINED113] Express POST /agent-config has no auth: Express route POST /agent-co… showcase/integrations/claude-sdk-typescript/src/a…:1116
high [MINED112] FastAPI POST /agent-config has no auth: Handler `agent_config_endpoi… showcase/integrations/claude-sdk-python/src/agent…:170
low File has no detected symbols: commitlint.config.js
low File has no detected symbols: showcase/playwright.env-routing.config.ts
low File has no detected symbols: showcase/integrations/claude-sdk-typescript/playw…
low File has no detected symbols: showcase/integrations/claude-sdk-typescript/next.…
low File has no detected symbols: showcase/integrations/claude-sdk-typescript/tests…
low Stray `console.log` in TS/JS — examples/showcases/open-mcp-client/apps/web/app/…
info `truncate` class without `title=` for hover reveal — examples/showcases/multi-a…
info `truncate` class without `title=` for hover reveal — examples/showcases/mcp-dem…
low Stray `console.log` in TS/JS — examples/showcases/mcp-demo/src/components/mcp-c…
critical Possible secret in showcase/harness/src/cli/config.ts showcase/harness/src/cli/config.ts:47

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/5c865d8d-bd31-4274-81bf-8558cfd5f077/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5c865d8d-bd31-4274-81bf-8558cfd5f077/

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.