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.

Yevheni55/POS

https://github.com/Yevheni55/POS · scanned 2026-06-16 01:05 UTC (2 months, 1 week ago)

228 raw signals (0 security + 228 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
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 57.1/100 with 100.0% coverage. It contains 2359 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 228 findings — concentrated in quality (101), security (55), api (52). Risk profile is high: 0 critical, 2 high, 73 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 157 of 228 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 api Wiring conf 1.00 Dangling fetch: GET http://localhost:${process.env.PORT || 3080}/api/reports/z-report?date=${date} (server/lib/print/z-report.js:29)
`server/lib/print/z-report.js:29` calls `GET http://localhost:${process.env.PORT || 3080}/api/reports/z-report?date=${date}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/reports/z-report` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/verify-manager (js/pos-payments.js:1000)
`js/pos-payments.js:1000` calls `POST /auth/verify-manager` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/verify-manager` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — admin/pages/reports.js:937
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 — js/dochadzka.js:71
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 — js/kitchen.js:436
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 — js/pos-payments.js:304
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 — scripts/check-portos-profile-on-kasa.mjs:5
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 — server/routes/ttlock.js:47
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 — server/scripts/portos-baud-scan.mjs:34
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 — server/scripts/portos-printer-test.mjs:15
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 authority lacks a verifier contract: .claude/admin-impl-contract.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/admin-impl-contract.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .cursor/rules/autonomous-deploy.mdc
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.cursor/rules/autonomous-deploy.mdc VerificationCursor rule
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
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, ci, lockfile. 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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
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 hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in server/routes/public-menu.js:82
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
server/routes/public-menu.js:82 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/components/command-palette.js:185
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/components/command-palette.js:185 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/components/tab-shell.js:37
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/components/tab-shell.js:37 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/components/toast-undo.js:112
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/components/toast-undo.js:112 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/index.html:340
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/index.html:340 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/assets.js:174
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/assets.js:174 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/audit.js:114
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/audit.js:114 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/cashflow.js:96
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/cashflow.js:96 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/dashboard.js:23
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/dashboard.js:23 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/dochadzka.js:195
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/dochadzka.js:195 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/fiscal-documents.js:31
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/fiscal-documents.js:31 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/forecasts.js:45
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/forecasts.js:45 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/ingredients.js:99
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/ingredients.js:99 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/inventory-audit.js:94
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/inventory-audit.js:94 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/inventory-dashboard.js:107
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/inventory-dashboard.js:107 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/menu.js:90
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/menu.js:90 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/payments.js:118
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/payments.js:118 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/purchase-orders.js:155
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/purchase-orders.js:155 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/recipes.js:173
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/recipes.js:173 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/reports.js:76
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/reports.js:76 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/season.js:50
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/season.js:50 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/settings.js:503
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/settings.js:503 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/shisha.js:68
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/shisha.js:68 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/staff.js:93
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/staff.js:93 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/stock-movements.js:89
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/stock-movements.js:89 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/storno.js:83
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/storno.js:83 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/suppliers.js:50
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/suppliers.js:50 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/supplies.js:43
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/supplies.js:43 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/tables.js:63
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/tables.js:63 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/weekly.js:66
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/weekly.js:66 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/write-offs.js:189
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/write-offs.js:189 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/pages/zam-spotreba.js:55
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/pages/zam-spotreba.js:55 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/router.js:299
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/router.js:299 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in api.js:551
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
api.js:551 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in components/loading.js:129
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
components/loading.js:129 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/dochadzka.js:35
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/dochadzka.js:35 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/kitchen.js:174
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/kitchen.js:174 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pos-init.js:577
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pos-init.js:577 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pos-mobile.js:50
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pos-mobile.js:50 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pos-orders.js:1154
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pos-orders.js:1154 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pos-payments.js:403
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pos-payments.js:403 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pos-render.js:191
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pos-render.js:191 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pos-state.js:16
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pos-state.js:16 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pos-ui.js:38
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pos-ui.js:38 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in login.html:443
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
login.html:443 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pos-design-demo.html:1749
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pos-design-demo.html:1749 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in web/index.html:1449
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
web/index.html:1449 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in admin/pages/purchase-orders.js:484
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
admin/pages/purchase-orders.js:484 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in js/pos-orders.js:374
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
js/pos-orders.js:374 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in admin/index.html:207
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
admin/index.html:207 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in api.js:120
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
api.js:120 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in js/kitchen.js:419
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
js/kitchen.js:419 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in js/pos-mobile.js:472
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
js/pos-mobile.js:472 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/export-surfspirit-menu.mjs:19
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/export-surfspirit-menu.mjs:19 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/lib/backup.js:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/lib/backup.js:15 Node child process
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 112 placeholder/mock markers across 26 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 network Security conf 1.00 Privileged port 4 in use
Port 4 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
Dockerfile Ports
low System graph quality Integrity conf 1.00 21 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ALLOWED_ORIGINS`, `BACKUP_DIR`, `BACKUP_RETENTION_DAYS`, `BUILD_VERSION`, `DEPLOY_HOST`, `DISABLE_PIN_RATE_LIMIT`, `HTTPS_PORT`, `KASA_BASE` + 13 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
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 93 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:1 containersPinned dependencies
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — js/pos-render.js:491
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
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 dependencies conf 1.00 Node manifest has dependencies but no lockfile: package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `pos_topItems_v1` in js/pos-state.js:32
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 `print_copy` in server/lib/portos.js:459
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 `print_copy` in server/test/routes/payments.portos.test.js:420
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 — admin/pages/recipes.js:798
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 — js/kitchen.js:468
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 — js/pos-init.js:249
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 — server/db/seed.js:15
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 — server/jobs/paragon-sync.js:31
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 — server/lib/forecast/engine.js:322
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 — server/lib/portos-sync-job.js:70
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 — server/lib/print/network.js:73
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 — server/lib/print/queue.js:26
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 — server/lib/weather.js:143
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 — server/routes/inventory.js:226
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 — server/routes/invoice-scan.js:140
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 — server/routes/ttlock.js:197
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 — server/server.js:74
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 api Wiring conf 1.00 Unused endpoint: GET /cashflow/summary?
`admin/pages/cashflow.js` declares `GET /cashflow/summary?` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /cashflow?
`admin/pages/cashflow.js` declares `GET /cashflow?` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /company-profile
`api.js` declares `GET /company-profile` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /company-profile/portos-compare
`api.js` declares `GET /company-profile/portos-compare` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /discounts
`js/pos-render.js` declares `GET /discounts` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /discounts/all
`admin/pages/settings.js` declares `GET /discounts/all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /fiscal-documents/
`api.js` declares `GET /fiscal-documents/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /fiscal-documents/search?
`api.js` declares `GET /fiscal-documents/search?` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /integrations/portos/status
`api.js` declares `GET /integrations/portos/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /inventory/suppliers
`admin/pages/cashflow.js` declares `GET /inventory/suppliers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /menu
`api.js` declares `GET /menu` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /orders
`js/pos-state.js` declares `GET /orders` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /orders/table/
`js/pos-state.js` declares `GET /orders/table/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /payments/
`api.js` declares `GET /payments/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /payments/history
`api.js` declares `GET /payments/history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /printers
`admin/pages/settings.js` declares `GET /printers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /reports/weather?from=
`admin/pages/weekly.js` declares `GET /reports/weather?from=` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /reports/weekly?from=
`admin/pages/weekly.js` declares `GET /reports/weekly?from=` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /reports/z-report?date=
`js/pos-init.js` declares `GET /reports/z-report?date=` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /shifts/current
`js/pos-init.js` declares `GET /shifts/current` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /shifts/current/summary
`js/pos-init.js` declares `GET /shifts/current/summary` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /storno-basket
`js/pos-state.js` declares `GET /storno-basket` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /tables
`js/pos-init.js` declares `GET /tables` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /zones
`js/pos-state.js` declares `GET /zones` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /cashflow/
`admin/pages/cashflow.js` declares `PATCH /cashflow/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /cashflow
`admin/pages/cashflow.js` declares `POST /cashflow` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /company-profile/sync-from-portos
`api.js` declares `POST /company-profile/sync-from-portos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /discounts
`admin/pages/settings.js` declares `POST /discounts` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /fiscal-documents/
`api.js` declares `POST /fiscal-documents/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /orders
`js/pos-ui.js` declares `POST /orders` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /orders/
`js/pos-payments.js` declares `POST /orders/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /paragons
`js/pos-payments.js` declares `POST /paragons` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /payments
`js/pos-payments.js` declares `POST /payments` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /payments/
`api.js` declares `POST /payments/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /print/kitchen
`js/pos-payments.js` declares `POST /print/kitchen` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /print/lockcode
`js/pos-init.js` declares `POST /print/lockcode` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /print/paragon
`js/pos-payments.js` declares `POST /print/paragon` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /print/pre-bill
`js/pos-payments.js` declares `POST /print/pre-bill` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /printers
`admin/pages/settings.js` declares `POST /printers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /printers/
`admin/pages/settings.js` declares `POST /printers/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /shifts/close
`js/pos-init.js` declares `POST /shifts/close` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /shifts/open
`js/pos-init.js` declares `POST /shifts/open` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /storno-basket
`js/pos-orders.js` declares `POST /storno-basket` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /storno-basket/
`js/pos-render.js` declares `POST /storno-basket/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /ttlock/passcode
`js/pos-init.js` declares `POST /ttlock/passcode` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /company-profile
`api.js` declares `PUT /company-profile` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /discounts/
`admin/pages/settings.js` declares `PUT /discounts/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /orders/
`js/pos-ui.js` declares `PUT /orders/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /printers/
`admin/pages/settings.js` declares `PUT /printers/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /tables/
`js/pos-state.js` declares `PUT /tables/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: admin/pages/dochadzka.js (1239 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: admin/pages/purchase-orders.js (1369 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: admin/pages/reports.js (1570 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: admin/pages/settings.js (1280 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/pos-orders.js (1907 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/pos-payments.js (1260 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/pos-render.js (1324 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/bb68053d-15c9-481c-a8b3-db0f38ff31b3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/bb68053d-15c9-481c-a8b3-db0f38ff31b3/

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.