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

Scan timing: clone 2.79s · analysis 14.71s · 1.9 MB · GitHub preflight 413ms

tropical-algae/TABlog

https://github.com/tropical-algae/TABlog · scanned 2026-06-05 18:26 UTC (4 days, 19 hours ago) · 10 languages

132 raw signals (86 security + 46 graph) 39th percentile · Javascript · small (2-20K LoC) System graph score 80 (lower by 22)

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

Complete repo analysis

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

JSON
Combined
73.9
/100
Security checks
68
78 findings
System graph
80
88.9% cov · 13 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 100.0 0.15 15.00
security_score 47.8 0.25 11.95
testing_score 0.0 0.20 0.00
documentation_score 69.7 0.15 10.46
practices_score 77.0 0.15 11.55
code_quality 80.0 0.10 8.00
Overall 1.00 57.0
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 30 Medium 34 Low 14 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 78 System graph 13 Crowd 0 Layer: Quality 15 Software 63 Cicd 5 Security 2 Api 1 Frontend 2 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 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
  • medium npm package `stylelint-config-standard` is 2 major version(s) behind (38.0.0 ->… package.json
  • low File has no detected symbols: vite.config.js
  • low Stray `console.log` in TS/JS — vite.config.js:12
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/8c21307b-38c7-4a9c-897b-75981cf3a755/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8c21307b-38c7-4a9c-897b-75981cf3a755/

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.