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.
38 of your 41 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.89s · analysis 4.19s · 2.5 MB · GitHub preflight 673ms

pandas-dev/pandas-stubs

https://github.com/pandas-dev/pandas-stubs · scanned 2026-06-05 18:25 UTC (4 days, 19 hours ago) · 10 languages

86 raw signals (40 security + 46 graph) 81st percentile · Python · medium (20-100K LoC) System graph score 100 (lower by 20)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
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 92.0 0.20 18.40
documentation_score 72.0 0.15 10.80
practices_score 75.0 0.15 11.25
code_quality 58.4 0.10 5.84
Overall 1.00 80.3
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 1 finding
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.
1 matching finding on this repo
  • low Near-duplicate function bodies in 2 places
View all duplicates & near-duplicates findings →
Commented-out code 3 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/`.
3 matching findings on this repo
  • info Commented-code block (9 lines) in tests/_typing.py:1
  • info Commented-code block (5 lines) in tests/series/test_series.py:502
  • info Commented-code block (5 lines) in tests/series/test_sub.py:239
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/27af6abe-159e-456b-919a-51947cd83081/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/27af6abe-159e-456b-919a-51947cd83081/

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.