google-ai-edge/LiteRT

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.

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

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 136.99s for a 240.6 MB repo slow.
Repobility's analysis ran in 34.53s after the clone landed.

https://github.com/google-ai-edge/LiteRT · scanned 2026-06-05 19:08 UTC (4 days, 17 hours ago) · 10 languages

694 raw signals (224 security + 470 graph) 11/13 scanners ran 48th percentile · C · large (100-500K LoC) System graph score 76 (lower by 9)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 17 hours ago · v2 · 250 actionable findings from 2 signal sources. 184 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 167 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	40.0	0.15	6.00
`security_score`	100.0	0.25	25.00
`testing_score`	24.0	0.20	4.80
`documentation_score`	100.0	0.15	15.00
`practices_score`	67.0	0.15	10.05
`code_quality`	60.0	0.10	6.00
Overall		1.00	66.8

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 19 Medium 21 Low 113 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 83 System graph 167 Crowd 0 Layer: Quality 150 Security 15 Cicd 9 Software 56 Frontend 15 Hardware 1 Api 4

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 5 places
low Near-duplicate function bodies in 3 places
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 8 places

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `_decode_error_legacy` in tflite/python/authoring/a…

View all legacy markers findings →

Commented-out code 29 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 (5 lines) in configure.py:487
info Commented-code block (6 lines) in litert/js/packages/core/src/datatypes.ts:97
info Commented-code block (8 lines) in litert/python/litert_wrapper/environment_wrap…
info Commented-code block (6 lines) in litert/python/tools/flatbuffer_utils.py:436
info Commented-code block (5 lines) in litert/python/tools/model_utils/shard/_shard.…
info Commented-code block (8 lines) in litert/python/tools/model_utils/test/match_te…
info Commented-code block (5 lines) in litert/python/tools/model_utils/dialect/tfl/_…
info Commented-code block (5 lines) in litert/python/aot/vendors/samsung/target.py:1
info Commented-code block (5 lines) in litert/python/aot/core/aot_types.py:234
info Commented-code block (6 lines) in ci/tools/python/wheel/utils/wheel_builder.py:…
info Commented-code block (8 lines) in ci/tools/python/vendor_sdk/intel/setup.py:51
info Commented-code block (5 lines) in ci/tools/python/vendor_sdk/qualcomm/setup.py:…

View all commented-out code findings →

Config drift 5 findings

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.

5 matching findings on this repo

low File has no detected symbols: litert/js/packages/tfjs_interop/eslint.config.js
low File has no detected symbols: litert/js/packages/wasm_utils/eslint.config.js
low File has no detected symbols: litert/js/packages/core/eslint.config.js
low File has no detected symbols: litert/js/packages/eslint_config/eslint.config.js
info Commented-code block (5 lines) in configure.py:487

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/c821ada3-5fc9-43d2-8dc4-4379e80cef2e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c821ada3-5fc9-43d2-8dc4-4379e80cef2e/

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.