protocolbuffers/protobuf

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.

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

Scan timing: clone 7.51s · analysis 15.59s · 101.7 MB · GitHub API rate-limit (preflight)

https://github.com/protocolbuffers/protobuf · scanned 2026-06-05 08:30 UTC (5 days, 20 hours ago) · 10 languages

678 raw signals (196 security + 482 graph) 11/13 scanners ran 69th percentile · C · huge (>500K LoC) System graph score 90 (lower by 14)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 123 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	65.0	0.15	9.75
`security_score`	100.0	0.25	25.00
`testing_score`	58.0	0.20	11.60
`documentation_score`	99.0	0.15	14.85
`practices_score`	79.0	0.15	11.85
`code_quality`	26.0	0.10	2.60
Overall		1.00	75.6

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 1 High 7 Medium 8 Low 93 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 68 System graph 123 Crowd 0 Layer: Quality 144 Software 39 Security 5 Cicd 2 Frontend 1

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

4 matching findings on this repo

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

View all duplicates & near-duplicates findings →

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

9 matching findings on this repo

low Very large file: compatibility/smoke/v21.12/legacy_gencode_test/proto3/Proto3Ge…
low Very large file: compatibility/smoke/v3.19.0/legacy_gencode_test/proto3/Proto3G…
low Very large file: compatibility/smoke/v3.11.0/legacy_gencode_test/proto3/Proto3G…
low Very large file: compatibility/smoke/v3.20.0/legacy_gencode_test/proto3/Proto3G…
low Very large file: compatibility/smoke/v26.0/legacy_gencode_test/proto3/Proto3Gen…
low Very large file: compatibility/smoke/v32.1/legacy_gencode_test/proto3/Proto3Gen…
low Very large file: compatibility/smoke/v3.8.0/legacy_gencode_test/proto3/Proto3Ge…
low Very large file: compatibility/smoke/v3.0.0/legacy_gencode_test/proto3/Proto3Ge…
low Very large file: compatibility/smoke/v25.8/legacy_gencode_test/proto3/Proto3Gen…

View all legacy markers findings →

Commented-out code 26 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 (11 lines) in benchmarks/compare.py:21
info Commented-code block (11 lines) in benchmarks/gen_upb_binary_c.py:21
info Commented-code block (11 lines) in benchmarks/gen_synthetic_protos.py:21
info Commented-code block (11 lines) in benchmarks/gen_protobuf_binary_cc.py:21
info Commented-code block (11 lines) in upb/bazel/private/oss/amalgamate.py:21
info Commented-code block (11 lines) in upb/cmake/staleness_test.py:19
info Commented-code block (11 lines) in upb/cmake/staleness_test_lib.py:21
info Commented-code block (11 lines) in docs/upb/render.py:21
info Commented-code block (11 lines) in python/minimal_test.py:19
info Commented-code block (5 lines) in python/google/protobuf/text_encoding.py:64
info Commented-code block (5 lines) in python/google/protobuf/message.py:182
info Commented-code block (5 lines) in python/google/protobuf/descriptor.py:520

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/e1cb783f-3f7f-43d8-b2ed-ab3d67b65489/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e1cb783f-3f7f-43d8-b2ed-ab3d67b65489/

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.