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.

gallery

https://github.com/google-ai-edge/gallery.git · scanned 2026-05-17 03:24 UTC (12 hours, 56 minutes ago) · 10 languages

45 findings (21 legacy + 24 scanner) Scanner says 90 (lower by 33)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 12 hours, 56 minutes ago · v2 · 33 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
Severity distribution — click a segment to filter
Active filters: severity: medium × excluding tests × Reset all
Severity: Critical 0 High 5 Medium 4 Low 21 Source: Legacy 21 9-layer 12 Crowd 0 Layer: Security 3 Quality 18 Software 3 Api 1 Frontend 2 Cicd 6
Scan summary Repository scanned at 89.7/100 with 77.8% coverage. It contains 553 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 12 findings — concentrated in cicd (6), frontend (2), quality (2). Risk profile is low: 0 critical, 0 high, 3 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 4 of 33 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium Legacy security path_traversal conf 1.00 [SEC012] ZipSlip — Archive Path Traversal: Archive extraction without path validation allows writing files outside the target directory.
Validate extracted paths with os.path.realpath() and ensure they stay within the target directory.
Android/src/app/src/main/java/com/google/ai/edge/gallery/worker/DownloadWorker.kt:283 path_traversallegacy
medium 9-layer cicd supply-chain conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/static.yml supply-chaingithub-actionsleast-privilege
medium 9-layer security coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). Either auth lives in custom code, in a separate service, or is missing.
coverageauth
medium 9-layer quality tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 5 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
testscoverage
{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}
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/329edd7e-4b0b-4a56-a4f1-b89a21424c7f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/329edd7e-4b0b-4a56-a4f1-b89a21424c7f/

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.