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.
Sign up free Scan another repo

tensorflow/tensorflow

https://github.com/tensorflow/tensorflow.git · scanned 2026-05-17 20:03 UTC (2 weeks, 4 days ago) · 10 languages

3589 findings (181 legacy + 3408 scanner) 8/10 scanners ran Scanner says 81 (lower by 3)

File as issue Image v2 schema
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 4 days ago · v2 · 181 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
77.0
/100
Repobility
73
181 legacy
9-layer
81
100.0% cov · 0 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 117 Medium 12 Low 51 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 181 9-layer 0 Crowd 0 Layer: Security 4 Cicd 106 Quality 71

Top 0 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

No actionable gaps — clean repo.

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/3d16a5ed-5b1f-411d-8295-4102918a13a1/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/3d16a5ed-5b1f-411d-8295-4102918a13a1/

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.