jaktestowac/rolnopol

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.

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)

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

88.9% cov · 180 findings

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

Exclude dismissed / FP Exclude test files

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.

Legacy markers 2 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

2 matching findings on this repo

low Old/deprecated-named symbol `view_legacy` in public/swagger/swagger-ui-es-bundl…
low Old/deprecated-named symbol `view_legacy` in public/swagger/swagger-ui.js:6083

View all legacy markers findings →

Commented-out code 8 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

8 matching findings on this repo

info Commented-code block (5 lines) in services/chaos-engine.service.js:9
info Commented-code block (6 lines) in public/js/app.js:391
info Commented-code block (5 lines) in public/js/pages/marketplace.js:1058
info Commented-code block (6 lines) in public/js/pages/staff-fields-assign.js:1238
info Commented-code block (12 lines) in public/js/pages/terminal-command-system.js:1…
info Commented-code block (5 lines) in public/js/pages/rolnopolmap.js:174
info Commented-code block (10 lines) in public/js/pages/buddy-page.js:129
info Commented-code block (6 lines) in plugins/plugin-template/index.js:38

View all commented-out code findings →

Config drift 2 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.

2 matching findings on this repo

medium No CI/CD configuration found
low File has no detected symbols: vitest.config.ts

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/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.