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.
Sign up free Scan another repo
34 of your 124 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.65s · analysis 21.78s · 3.3 MB · GitHub API rate-limit (preflight)

hackclub/hackatime

https://github.com/hackclub/hackatime · scanned 2026-06-05 17:54 UTC (4 days, 21 hours ago) · 10 languages

201 raw signals (117 security + 84 graph) System graph score 69 (lower by 6)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
65.2
/100
Security checks
61
76 findings
System graph
69
100.0% cov · 21 findings
Critical
3
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 36.2 0.25 9.05
testing_score 61.0 0.20 12.20
documentation_score 60.8 0.15 9.12
practices_score 86.0 0.15 12.90
code_quality 71.9 0.10 7.19
Overall 1.00 63.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 3 High 44 Medium 18 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 76 System graph 21 Crowd 0 Layer: Quality 16 Security 33 Software 25 Cicd 17 Api 1 Frontend 1 Network 1 Hardware 3

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.

Config drift 2 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.
2 matching findings on this repo
  • low File has no detected symbols: vite.config.ts
  • low File has no detected symbols: svelte.config.js
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/56bb2fd3-05ef-451b-9d47-d06ccc7ed7eb/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/56bb2fd3-05ef-451b-9d47-d06ccc7ed7eb/

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.