google/skia

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.

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

https://github.com/google/skia · scanned 2026-06-05 14:20 UTC (5 days, 5 hours ago) · 10 languages

801 raw signals (55 security + 746 graph) 11/13 scanners ran 9th percentile · Cpp · medium (20-100K LoC) System graph score 53 (higher by 5)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 5 hours ago · v2 · 377 actionable findings from 2 signal sources. 29 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 · 357 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`	17.0	0.20	3.40
`documentation_score`	54.0	0.15	8.10
`practices_score`	32.0	0.15	4.80
`code_quality`	80.0	0.10	8.00
Overall		1.00	58.3

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 0 High 33 Medium 117 Low 165 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 20 System graph 357 Crowd 0 Layer: Quality 150 Security 10 Software 80 Frontend 43 Network 4 Hardware 40 Cicd 1 Api 49

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

5 matching findings on this repo

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

View all duplicates & near-duplicates findings →

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

3 matching findings on this repo

low File has no detected symbols: modules/canvaskit/tests/legacy_init.js
low Stray `console.log` in TS/JS — modules/canvaskit/tests/legacy_test_reporter.js:…
low Stray `console.log` in TS/JS — modules/canvaskit/tests/legacy_init.js:7

View all legacy markers findings →

Commented-out code 34 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 (7 lines) in PRESUBMIT.py:518
info Commented-code block (5 lines) in resources/sksl/es2_conformance/import_conform…
info Commented-code block (7 lines) in modules/canvaskit/memory.js:114
info Commented-code block (8 lines) in modules/canvaskit/webgl.js:312
info Commented-code block (6 lines) in modules/canvaskit/matrix.js:2
info Commented-code block (6 lines) in modules/canvaskit/color.js:5
info Commented-code block (7 lines) in modules/canvaskit/paragraph.js:162
info Commented-code block (6 lines) in modules/canvaskit/interface.js:99
info Commented-code block (5 lines) in modules/canvaskit/tests/font_test.js:290
info Commented-code block (7 lines) in modules/canvaskit/tests/canvas_test.js:418
info Commented-code block (8 lines) in modules/canvaskit/htmlcanvas/canvas2dcontext.…
info Commented-code block (9 lines) in modules/canvaskit/htmlcanvas/radialgradient.j…

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

medium No CI/CD configuration found

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/1a93f112-d349-4973-9d25-a212da316793/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1a93f112-d349-4973-9d25-a212da316793/

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.