kvrajumca/skills-getting-started-with-github-copilot

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.

Scan timing: clone 3.26s · analysis 0.1s · 2.6 MB · GitHub preflight 471ms

kvrajumca/skills-getting-started-with-github-copilot

https://github.com/kvrajumca/skills-getting-started-with-github-copilot.git · scanned 2026-05-28 22:38 UTC (1 week ago) · 10 languages

172 findings (38 legacy + 134 scanner) 78th percentile · Javascript · tiny (<2K LoC) Scanner says 84 (lower by 5)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week ago · v2 · 105 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

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	70.0	0.15	10.50
`security_score`	95.5	0.25	23.88
`testing_score`	70.0	0.20	14.00
`documentation_score`	75.0	0.15	11.25
`practices_score`	77.0	0.15	11.55
`code_quality`	80.0	0.10	8.00
Overall		1.00	79.2

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 28 Medium 49 Low 25 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 38 9-layer 67 Crowd 0 Layer: Quality 5 Security 5 Software 30 Frontend 1 Cicd 63 Api 1

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

4 matching findings on this repo

medium Public web service has no security.txt .well-known/security.txt
info [MINED044] Js Console Log Prod: console.log left in code. Should be replaced wi… src/static/app.js:40
high [SEC135] Auth/permission check missing on AI-generated endpoint: Mutating HTTP … src/app.py:55
high FastAPI POST /activities/{activity_name}/signup has no auth src/app.py:56

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/8c3cad20-8007-4048-a4ad-406cb5d0bbce/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8c3cad20-8007-4048-a4ad-406cb5d0bbce/

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.