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

Scan timing: clone 3.05s · analysis 20.88s · 12.3 MB · GitHub API rate-limit (preflight)

hashgraph-online/hol-guard

https://github.com/hashgraph-online/hol-guard · scanned 2026-06-06 00:56 UTC (4 days, 1 hour ago) · 10 languages

680 raw signals (272 security + 408 graph) 27th percentile · Python · large (100-500K LoC) System graph score 74 (lower by 7)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 1 hour ago · v2 · 315 actionable findings from 2 signal sources. 136 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 85.0 0.15 12.75
security_score 18.3 0.25 4.58
testing_score 100.0 0.20 20.00
documentation_score 95.0 0.15 14.25
practices_score 96.0 0.15 14.40
code_quality 7.0 0.10 0.70
Overall 1.00 66.7
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 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 3 places repo-level
  • low Near-duplicate function bodies in 8 places
  • low Near-duplicate function bodies in 6 places
  • low Near-duplicate function bodies in 5 places repo-level
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 `req_legacy` in tests/test_guard_approval_store_ded…
View all legacy markers findings →
Config drift 3 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.
3 matching findings on this repo
  • low File has no detected symbols: dashboard/playwright.config.ts
  • low File has no detected symbols: dashboard/vite.config.ts
  • low Old/deprecated-named symbol `test_migrate_guard_home_state_copies_guard_db_with…
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/9defc105-15ae-4694-847f-5be73fe34511/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9defc105-15ae-4694-847f-5be73fe34511/

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.