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

Scan timing: clone 10.74s · analysis 9.22s · 20.2 MB · GitHub API rate-limit (preflight)

Szybet/InkWatchy

https://github.com/Szybet/InkWatchy · scanned 2026-06-05 22:54 UTC (4 days, 7 hours ago) · 10 languages

92 raw signals (62 security + 30 graph) 0th percentile · C · medium (20-100K LoC) System graph score 76 (lower by 33)

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

Complete repo analysis

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

JSON
Combined
63.3
/100
Security checks
51
30 findings
System graph
76
88.9% cov · 15 findings
Critical
1
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 65.0 0.15 9.75
security_score 45.8 0.25 11.45
testing_score 0.0 0.20 0.00
documentation_score 60.0 0.15 9.00
practices_score 40.0 0.15 6.00
code_quality 60.2 0.10 6.02
Overall 1.00 42.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 11 Medium 10 Low 10 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 30 System graph 15 Crowd 0 Layer: Software 12 Cicd 5 Security 5 Quality 18 Api 1 Hardware 3 Frontend 1

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 1 finding
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.
1 matching finding on this repo
  • medium No CI/CD configuration found
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/ff8d3a4c-99fa-496d-8554-9fc731687680/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ff8d3a4c-99fa-496d-8554-9fc731687680/

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.