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

Scan timing: clone 1.3s · analysis 0.64s · 0.7 MB · GitHub API rate-limit (preflight)

vinayluffy-12/payrollproject

https://github.com/vinayluffy-12/payrollproject.git · scanned 2026-05-28 06:07 UTC (1 week, 1 day ago) · 10 languages

270 findings (88 legacy + 182 scanner) 32nd percentile · Javascript · small (2-20K LoC)

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

Complete repo analysis

Last scanned 1 week, 1 day ago · v2 · 179 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
54.7
/100
Repobility
63
88 legacy
9-layer
46
100.0% cov · 91 gaps
Critical
6
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 75.0 0.15 11.25
security_score 65.9 0.25 16.48
testing_score 0.0 0.20 0.00
documentation_score 40.0 0.15 6.00
practices_score 50.0 0.15 7.50
code_quality 69.4 0.10 6.94
Overall 1.00 48.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 6 High 58 Medium 19 Low 81 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 88 9-layer 91 Crowd 0 Layer: Quality 51 Cicd 26 Software 34 Frontend 8 Hardware 7 Security 1 Api 52

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
FastAPI POST `check_payroll_run` without auth dependency — payrollos/fraud-service/main.py:48
GapSeverity.HIGH Layer.SECURITY score 0.537
Why: high severity · OWASP-class risk
Fix: Add `user = Depends(get_current_user)` to the function signature in payrollos/fraud-service/main.py:48.
payrollos/fraud-service/main.py:48
#2
Dangling fetch: POST https://api.openai.com/v1/chat/completions (payrollos/backend/src/routes/reports.js:127)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#3
Dangling fetch: POST http://127.0.0.1:8000/api/v1/fraud/check-run (payrollos/backend/src/routes/payroll.js:157)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#4
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
payrollos/.github/workflows/ci-cd.yml:56
#5
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
payrollos/.github/workflows/ci-cd.yml:64
#6
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
payrollos/.github/workflows/ci-cd.yml:95
#7
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
payrollos/.github/workflows/ci-cd.yml:116
#8
Dockerfile runs as root: payrollos/frontend/Dockerfile
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity
#9
Dockerfile runs as root: payrollos/fraud-service/Dockerfile
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity
#10
Dockerfile runs as root: payrollos/backend/Dockerfile
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/5e3a4bfb-9ca7-4f09-bc7e-de3da5e404e0/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5e3a4bfb-9ca7-4f09-bc7e-de3da5e404e0/

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.