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

Safronus/ctyrlistkoteka

https://github.com/Safronus/ctyrlistkoteka · scanned 2026-06-15 23:59 UTC (2 months, 3 weeks ago)

135 raw signals (0 security + 135 graph)

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

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 135 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
80.2
/100
Security checks
80
0 findings
System graph
80
100.0% cov · 135 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 1 Medium 17 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 135 Crowd 0 Layer: Api 1 Frontend 22 Hardware 1 Security 9 Quality 102
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 80.2/100 with 100.0% coverage. It contains 1922 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 135 findings — concentrated in quality (102), frontend (22), security (9). Risk profile is high: 0 critical, 1 high, 17 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 38 of 135 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
CLAUDE.md:259 SecretsClaude instruction
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/app/admin/files/finds/qr-button.tsx:113
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/app/admin/qr/qr-generator-form.tsx:294
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/components/theme-script.tsx:30
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/app/admin/files/finds/upload-form.tsx:77
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/components/finds/random-find-showcase.tsx:68
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/app/admin/files/finds/qr-button.tsx:113
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/app/admin/files/finds/qr-button.tsx:113 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/app/admin/qr/qr-generator-form.tsx:294
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/app/admin/qr/qr-generator-form.tsx:294 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/theme-script.tsx:30
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/theme-script.tsx:30 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in next.config.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
next.config.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/prepare-upload.ts:56
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/prepare-upload.ts:56 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/app/admin/sync/pm2-restart-action.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/app/admin/sync/pm2-restart-action.ts:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/lib/admin/syncRunner.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/lib/admin/syncRunner.ts:3 Node child process
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 81 placeholder/mock markers across 33 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
7 test file(s) for 320 source file(s) (ratio 0.02). Consider adding integration or unit tests for critical paths.
Coverage
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — src/components/stats/calendar-heatmap-tabs.tsx:86
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — src/components/stats/top-finds-leaderboard.tsx:182
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — src/components/stats/top-locations-card.tsx:142
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph quality Integrity conf 1.00 12 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ABUSEIPDB_LOG_PATH`, `ABUSEIPDB_STATE_PATH`, `ADMIN_EXPECTED_ORIGIN`, `ADMIN_RP_ID`, `FAIL2BAN_BLOCKLIST_PATH`, `NEXT_PHASE`, `NEXT_PUBLIC_COMMIT_COUNT`, `PERMABAN_BACKUP_DIR` + 4 more. Add them (with a placeholder/comment) to .env.example so onbo…
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 100 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `rawOld` in src/app/admin/files/crops/rename-action.ts:45
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `rawOld` in src/app/admin/files/finds/rename-action.ts:46
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `rawOld` in src/app/admin/files/maps/rename-action.ts:103
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/apply-watermark.ts:105
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/prepare-upload.ts:301
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/seed.ts:281
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Complexity conf 1.00 Very large file: scripts/sync.ts (1974 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/[locale]/statistiky/page.tsx (2559 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/admin/audit/blocklist/page.tsx (1459 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/lib/queries/finds.ts (1525 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/lib/queries/locations.ts (1295 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/lib/queries/stats.ts (1947 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/b0a5df6f-7c45-4a7f-b281-1fb260fed1c3/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/b0a5df6f-7c45-4a7f-b281-1fb260fed1c3/

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.