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

Scan timing: clone 3.59s · analysis 15.97s · 1.6 MB · GitHub API rate-limit (preflight)

Azim-Ahmed/Automation-workflow

https://github.com/Azim-Ahmed/Automation-workflow · scanned 2026-06-05 16:56 UTC (5 days ago) · 10 languages

312 raw signals (278 security + 34 graph) 29th percentile · Javascript · tiny (<2K LoC) System graph score 80 (lower by 27)

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

Complete repo analysis

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

JSON
Combined
74.4
/100
Security checks
68
112 findings
System graph
80
66.7% cov · 17 findings
Critical
4
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 52.0 0.25 13.00
testing_score 23.0 0.20 4.60
documentation_score 38.7 0.15 5.81
practices_score 46.0 0.15 6.90
code_quality 78.7 0.10 7.87
Overall 1.00 53.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 4 High 34 Medium 49 Low 35 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 112 System graph 17 Crowd 0 Layer: Quality 14 Software 107 Api 1 Frontend 5 Security 1 Cicd 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/a26233f4-6f06-4682-bf0d-658632a042ab/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a26233f4-6f06-4682-bf0d-658632a042ab/

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.