docloulou/Wayland-Wheeltani

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.

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

https://github.com/docloulou/Wayland-Wheeltani · scanned 2026-05-18 14:47 UTC (2 weeks, 3 days ago) · 10 languages

61 findings (4 legacy + 57 scanner) Scanner says 85 (lower by 22)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 3 days ago · v3 · 23 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`	75.0	0.15	11.25
`security_score`	100.0	0.25	25.00
`testing_score`	0.0	0.20	0.00
`documentation_score`	60.0	0.15	9.00
`practices_score`	73.0	0.15	10.95
`code_quality`	70.0	0.10	7.00
Overall		1.00	63.2

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 10 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 4 9-layer 19 Crowd 0 Layer: Quality 5 Api 1 Frontend 1 Security 1 Cicd 15

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

3 matching findings on this repo

high [MINED003] Rust Unwrap In Prod: .unwrap() panics if None/Err. Acceptable in tes… crates/middle-scroll-linux/src/service.rs:198
high [MINED003] Rust Unwrap In Prod: .unwrap() panics if None/Err. Acceptable in tes… crates/middle-scroll-linux/src/config_loader.rs:374
high [MINED003] Rust Unwrap In Prod: .unwrap() panics if None/Err. Acceptable in tes… crates/middle-scroll-core/src/tests.rs:75

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/5e138d22-79f4-47be-9cce-509d04dc76b7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5e138d22-79f4-47be-9cce-509d04dc76b7/

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.