— Repobility public scan

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.

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

Scan timing: clone 4.12s · analysis 21.99s · 17.8 MB · GitHub API rate-limit (preflight)

github/copilot-sdk

https://github.com/github/copilot-sdk · scanned 2026-06-04 23:18 UTC (16 hours, 42 minutes ago) · 10 languages

1079 findings (223 legacy + 856 scanner) 12th percentile · Java · large (100-500K LoC) Scanner says 80 (lower by 14)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 16 hours, 41 minutes ago · v4 · 437 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

100.0% cov · 214 gaps

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	40.0	0.15	6.00
`security_score`	34.6	0.25	8.65
`testing_score`	100.0	0.20	20.00
`documentation_score`	100.0	0.15	15.00
`practices_score`	82.0	0.15	12.30
`code_quality`	44.7	0.10	4.47
Overall		1.00	66.4

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 25 High 158 Medium 26 Low 176 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 223 9-layer 214 Crowd 0 Layer: Security 7 Quality 202 Software 169 Api 1 Frontend 21 Cicd 37

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 109 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 Agent auto-approve or skip-permissions mode is easy to enable .github/workflows/java-smoke-test.yml:77
medium Bare except continues silently python/copilot/session.py:1709
medium Bare except continues silently python/copilot/session.py:1658
medium Bare except continues silently python/copilot/session_fs_provider.py:303
medium Bare except continues silently python/copilot/session_fs_provider.py:262
medium Bare except continues silently python/copilot/session_fs_provider.py:255
medium Bare except continues silently python/copilot/session_fs_provider.py:241
medium Bare except continues silently python/copilot/session_fs_provider.py:233
medium Bare except continues silently python/copilot/session_fs_provider.py:226
medium Bare except continues silently python/copilot/session_fs_provider.py:206
medium Bare except continues silently python/copilot/session_fs_provider.py:193
medium Bare except continues silently python/copilot/session_fs_provider.py:186

View all fragile runtime findings →

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

10 matching findings on this repo

low Legacy-named symbol `isNodeFullyDeprecated` in scripts/codegen/csharp.ts:37
low Legacy-named symbol `isSchemaDeprecated` in scripts/codegen/rust.ts:39
low Legacy-named symbol `import_legacy` in scripts/codegen/utils.ts:25
low Legacy-named symbol `isNodeFullyDeprecated` in scripts/codegen/go.ts:35
low Legacy-named symbol `isNodeFullyDeprecated` in scripts/codegen/python.ts:26
low Legacy-named symbol `isNodeFullyDeprecated` in scripts/codegen/typescript.ts:37
low Legacy-named symbol `import_legacy` in nodejs/test/session-event-codegen.test.t…
low Legacy-named symbol `pruneOld` in nodejs/test/e2e/rpc_server.e2e.test.ts:326
low Legacy-named symbol `pruneOld` in nodejs/src/generated/rpc.ts:10541
low Legacy-named symbol `import_legacy` in java/scripts/codegen/java.ts:22

View all legacy markers findings →

Commented-out code 24 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 test/harness/replayingCapiProxy.ts:109
info Commented-code block (5 lines) in scripts/codegen/csharp.ts:1870
info Commented-code block (6 lines) in scripts/codegen/rust.ts:819
info Commented-code block (5 lines) in scripts/codegen/utils.ts:911
info Commented-code block (6 lines) in scripts/codegen/go.ts:3506
info Commented-code block (5 lines) in scripts/codegen/python.ts:554
info Commented-code block (5 lines) in scripts/codegen/typescript.ts:288
info Commented-code block (11 lines) in nodejs/test/e2e/skills.e2e.test.ts:85
info Commented-code block (5 lines) in nodejs/test/e2e/pending_work_resume.e2e.test.…
info Commented-code block (6 lines) in nodejs/test/e2e/permissions.e2e.test.ts:59
info Commented-code block (7 lines) in nodejs/test/e2e/session_config.e2e.test.ts:342
info Commented-code block (6 lines) in nodejs/test/e2e/builtin_tools.e2e.test.ts:11

View all commented-out code findings →

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

7 matching findings on this repo

low File has no detected symbols: test/harness/vitest.config.ts
low File has no detected symbols: nodejs/eslint.config.js
low File has no detected symbols: nodejs/vitest.config.ts
low Very large file: java/src/main/java/com/github/copilot/rpc/SessionConfig.java (…
low Very large file: java/src/main/java/com/github/copilot/rpc/ResumeSessionConfig.…
info Commented-code block (7 lines) in nodejs/test/e2e/session_config.e2e.test.ts:342
info Commented-code block (7 lines) in python/e2e/test_session_config_e2e.py:240

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/5ef0a980-c2f9-417c-a367-43c5f959e224/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5ef0a980-c2f9-417c-a367-43c5f959e224/

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.