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.
132 of your 225 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 88.86s for a 74.4 MB repo slow.
  • Repobility's analysis ran in 3.93s after the clone landed.

fineanmol/Hacktoberfest2025

https://github.com/fineanmol/Hacktoberfest2025 · scanned 2026-06-05 14:12 UTC (5 days, 6 hours ago) · 10 languages

558 raw signals (202 security + 356 graph) 11/13 scanners ran 0th percentile · Cpp · medium (20-100K LoC) System graph score 56 (higher by 2)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 6 hours ago · v2 · 234 actionable findings from 2 signal sources. 146 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 40.0 0.15 6.00
security_score 100.0 0.25 25.00
testing_score 15.0 0.20 3.00
documentation_score 60.0 0.15 9.00
practices_score 59.0 0.15 8.85
code_quality 60.0 0.10 6.00
Overall 1.00 57.9
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

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 2 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.
2 matching findings on this repo
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 4 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 (5 lines) in Program's_Contributed_By_Contributors/Python_…
  • info Commented-code block (5 lines) in Program's_Contributed_By_Contributors/Python_…
  • info Commented-code block (5 lines) in Program's_Contributed_By_Contributors/Python_…
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/ed72e4d9-9637-4141-b743-4e459789d6e9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ed72e4d9-9637-4141-b743-4e459789d6e9/

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.