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.

zivtech/a11y-meta-skills

https://github.com/zivtech/a11y-meta-skills · scanned 2026-06-16 01:13 UTC (2 months, 1 week ago)

37 raw signals (0 security + 37 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 30 actionable findings from 1 signal source. 7 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 · 30 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 1 Medium 13 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 30 Crowd 0 Layer: Software 1 Api 1 Frontend 2 Security 6 Cicd 2 Quality 18

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

2 matching findings on this repo

low Near-duplicate function bodies in 3 places
low Near-duplicate function bodies in 2 places repo-level

View all duplicates & near-duplicates findings →

Commented-out code 4 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/`.

4 matching findings on this repo

info Commented-code block (6 lines) in evals/suites/chain/score_chain.py:33
info Commented-code block (9 lines) in evals/suites/webwright-benchmark/task-3a-dial…
info Commented-code block (5 lines) in ollama/score_common.py:4
info Commented-code block (7 lines) in ollama/run_cloud_benchmark.py:553

View all commented-out code 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/cb898be0-c88d-457c-80a4-dc2fb30b6d16/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/cb898be0-c88d-457c-80a4-dc2fb30b6d16/

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.