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 27.51s · analysis 6.26s · 41.8 MB · GitHub API rate-limit (preflight)

jaktestowac/rolnopol

https://github.com/jaktestowac/rolnopol · scanned 2026-06-06 01:09 UTC (4 days, 1 hour ago) · 10 languages

463 raw signals (89 security + 374 graph) 11/13 scanners ran 48th percentile · Javascript · large (100-500K LoC) System graph score 64 (higher by 10)

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

Complete repo analysis

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

JSON
Combined
70.8
/100
Security checks
78
52 findings
System graph
64
88.9% cov · 180 findings
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 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 100.0 0.20 20.00
documentation_score 45.0 0.15 6.75
practices_score 42.0 0.15 6.30
code_quality 70.0 0.10 7.00
Overall 1.00 74.0
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 6 High 35 Medium 20 Low 150 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 52 System graph 180 Crowd 0 Layer: Quality 69 Security 22 Software 53 Frontend 25 Cicd 1 Api 62

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

#1
Possible secret in helpers/logger-api.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in helpers/logger-api.js:146; move to env var / secrets manager.
helpers/logger-api.js:146
#2
Possible secret in services/admin.service.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in services/admin.service.js:433; move to env var / secrets manager.
services/admin.service.js:433
#3
Possible secret in public/swagger/swagger-ui-es-bundle-core.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in public/swagger/swagger-ui-es-bundle-core.js:13207; move to env var / secrets manager.
public/swagger/swagger-ui-es-bundle-core.js:13207
#4
Possible secret in public/swagger/swagger-ui-es-bundle-core.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in public/swagger/swagger-ui-es-bundle-core.js:13789; move to env var / secrets manager.
public/swagger/swagger-ui-es-bundle-core.js:13789
#5
Possible secret in public/swagger/swagger-ui-es-bundle-core.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in public/swagger/swagger-ui-es-bundle-core.js:18889; move to env var / secrets manager.
public/swagger/swagger-ui-es-bundle-core.js:18889
#6
Possible secret in public/swagger/swagger-ui.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in public/swagger/swagger-ui.js:7029; move to env var / secrets manager.
public/swagger/swagger-ui.js:7029
#7
Possible secret in public/swagger/swagger-ui.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in public/swagger/swagger-ui.js:7620; move to env var / secrets manager.
public/swagger/swagger-ui.js:7620
#8
Possible secret in public/swagger/swagger-ui.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in public/swagger/swagger-ui.js:12734; move to env var / secrets manager.
public/swagger/swagger-ui.js:12734
#9
Possible secret in public/js/pages/terminal-page.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in public/js/pages/terminal-page.js:264; move to env var / secrets manager.
public/js/pages/terminal-page.js:264
#10
Possible secret in public/js/pages/terminal-page.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in public/js/pages/terminal-page.js:335; move to env var / secrets manager.
public/js/pages/terminal-page.js:335

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/d26aa316-1e43-4a9b-9182-551eba4d6839/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d26aa316-1e43-4a9b-9182-551eba4d6839/

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.