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

viktordrukker/DeliveryCentral

https://github.com/viktordrukker/DeliveryCentral · scanned 2026-06-16 00:50 UTC (2 months, 1 week ago)

408 raw signals (94 security + 314 graph)

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

Complete repo analysis

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

JSON
Combined
57.1
/100
Security checks
57
8 findings
System graph
57
100.0% cov · 288 findings
Critical
11
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 11 High 3 Medium 30 Low 98 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 288 Crowd 0 Layer: Quality 193 Security 24 Frontend 16 Network 1 Hardware 9 Cicd 3 Api 50
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 9131 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 314 findings — concentrated in quality (186), api (50), security (42). Risk profile is high: 28 critical, 0 high, 29 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 136 of 296 actionable findings. 524 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical Security checks quality Practices conf 0.82 13 occurrences Foundry mined mock as real or placeholder: viktordrukker/DeliveryCentral
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
13 occurrences
repo-level (13 hits)
critical Security checks security auth conf 0.78 2 occurrences Foundry mined security auth guardrail gaps: viktordrukker/DeliveryCentral
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
2 occurrences
repo-level (2 hits)
critical System graph security Secrets conf 1.00 6 occurrences Possible secret in frontend/src/components/layout/AppShell.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 26, 27, 28, 29, 30, 31
frontend/src/components/layout/AppShell.tsx:26, 27, 28, 29, 30, 31 (6 hits)
critical System graph security Secrets conf 1.00 Possible secret in frontend/src/routes/admin/v2-soak-journeys.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
frontend/src/routes/admin/v2-soak-journeys.ts:79
critical System graph security Secrets conf 1.00 7 occurrences Possible secret in prisma/seeds/it-company-profile.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 2199, 2200, 2201, 2202, 2203, 2204, 2205
prisma/seeds/it-company-profile.ts:2199, 2200, 2201, 2202, 2203, 2204, 2205 (7 hits)
critical System graph security Secrets conf 1.00 8 occurrences Possible secret in scripts/jtbd-walker.cjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 26, 27, 28, 29, 30, 31, 32, 33
scripts/jtbd-walker.cjs:26, 27, 28, 29, 30, 31, 32, 33 (8 hits)
high Security checks quality Practices conf 0.84 3 occurrences Foundry mined bad chains: viktordrukker/DeliveryCentral
Comment chain pattern product: bad_chains Repo: viktordrukker/DeliveryCentral Thread: viktordrukker/DeliveryCentral#663 Outcome: claimed_resolved_unverified Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artif…
3 occurrences
repo-level (3 hits)
high Security checks quality Quality conf 0.76 18 occurrences Foundry mined schema ui api mismatch: viktordrukker/DeliveryCentral
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: supported_by_high_confidence_link Rep…
18 occurrences
repo-level (18 hits)
high Security checks quality Testing conf 0.78 40 occurrences Foundry mined test ci gap after feedback: viktordrukker/DeliveryCentral
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_verificati…
40 occurrences
repo-level (40 hits)
medium Security checks quality Practices conf 0.62 60 occurrences Foundry mined assumption checks: viktordrukker/DeliveryCentral
Comment chain pattern product: assumption_checks Repo: viktordrukker/DeliveryCentral Thread: viktordrukker/DeliveryCentral#734 Outcome: claimed_resolved_unverified Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_rea…
60 occurrences
repo-level (60 hits)
medium Security checks quality maintenance conf 0.70 69 occurrences Foundry mined blueprint gap alignment: viktordrukker/DeliveryCentral
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
69 occurrences
repo-level (69 hits)
medium Security checks quality Practices conf 0.70 5 occurrences Foundry mined unresolved feedback: viktordrukker/DeliveryCentral
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
5 occurrences
repo-level (5 hits)
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/components/help/MarkdownBody.tsx:6
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 — frontend/src/lib/api/setup.ts:244
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/lean-migration-soak-monitor.ts:67
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/verify-demo-consistency.ts:39
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/modules/notifications/infrastructure/adapters/fetch-teams-webhook.transport.ts:21
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 hardware Security conf 1.00 Dockerfile runs as root: ops/issue-reporter/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: ops/templates/caddy/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 Frontend route `/help/:slug` has no Link/navigate to it — frontend/src/routes/help/HelpArticleDetailPage.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
3 files, 3 locations
.github/workflows/build-and-stage-v2.yml
.github/workflows/build-and-stage.yml
.github/workflows/v2-soak-monitor.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in e2e/a11y/scripts/refresh-baseline.cjs:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
e2e/a11y/scripts/refresh-baseline.cjs:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-agent-ownership.cjs:37
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-agent-ownership.cjs:37 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-forward-only-approvals.cjs:54
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-forward-only-approvals.cjs:54 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-rbac.cjs:22
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-rbac.cjs:22 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-role-literals.cjs:23
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-role-literals.cjs:23 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-schema-migration-pairing.cjs:22
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-schema-migration-pairing.cjs:22 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/continuous-drift-monitor.cjs:36
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/continuous-drift-monitor.cjs:36 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/lib/drift-events.cjs:31
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/lib/drift-events.cjs:31 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/run-jest-suite.cjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/run-jest-suite.cjs:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/validation/run-operator-drill.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/validation/run-operator-drill.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/verify-seed.cjs:24
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/verify-seed.cjs:24 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/modules/setup/application/preflight-checks.ts:318
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/modules/setup/application/preflight-checks.ts:318 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/modules/setup/application/setup.service.ts:582
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/modules/setup/application/setup.service.ts:582 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 228 placeholder/mock markers across 114 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 3 in use
Port 3 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
ops/bootstrap-app.sh Ports
low System graph quality Integrity conf 1.00 70 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ACTOR_AUDIT_THRESHOLD`, `ADMIN_BEARER`, `AGENT_ID`, `API_BASE`, `API_BASE_URL`, `AUDIT_SWEEP_DISABLED`, `BACKEND_PUBLIC_URL`, `BACKEND_URL` + 62 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 187 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: alpine:3.19
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
ops/issue-reporter/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: caddy:2.9-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
ops/templates/caddy/Dockerfile:8 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: caddy:2.9-builder-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
ops/templates/caddy/Dockerfile:5 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: nginx:1.27-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
frontend/Dockerfile:44 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 3 occurrences 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.
lines 1, 9, 24
frontend/Dockerfile:1, 9, 24 (3 hits)
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-bookworm-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 1, 46
Dockerfile:1, 46 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 67, 70, 91
.github/workflows/v2-playwright-baseline.yml:67, 70, 91 (3 hits)
CI/CD securitySupply chainGithub actions
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 `1_old` in test/integration/migration-categories.spec.ts:152
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 `20260418_project_radiator_v1` in test/integration/migration-contracts.generated.spec.ts:1336
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 `block__copy` in frontend/src/routes/admin/IntegrationsAdminPage.tsx:202
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 `block__copy` in frontend/src/routes/integrations/IntegrationsPage.tsx:84
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 `block__copy` in frontend/src/routes/people/EmployeeDetailsPage.tsx:534
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 `block__copy` in frontend/src/routes/work-evidence/WorkEvidencePage.tsx:174
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 `dayOld` in frontend/src/routes/dashboard/rm-sections/RmActionItems.test.tsx:56
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 `editor__copy` in frontend/src/components/admin/DictionaryEditor.tsx:108
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 `editor__copy` in frontend/src/components/admin/SendTestPanel.tsx:29
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 `editor__copy` in frontend/src/components/common/AuthTokenField.tsx:30
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 `editor__copy` in frontend/src/components/teams/MemberSelector.tsx:22
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 `editor__copy` in frontend/src/components/teams/TeamDetails.tsx:112
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 `editor__copy` in frontend/src/routes/projects/tabs/TeamVendorsTab.tsx:325
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 `mapPositionFillStatusToLegacy` in src/modules/project-positions/domain/value-objects/position-fill-status.ts:181
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 `panel__copy` in frontend/src/components/common/GovernanceOverridePanel.tsx:38
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 `panel__copy` in frontend/src/components/exceptions/ExceptionDetailPanel.tsx:91
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 `panel__copy` in frontend/src/components/projects/AnomalyPanel.tsx:15
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 cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
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 — e2e/a11y/axe-baseline.spec.ts:161
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 — prisma/seed.ts:424
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/check-soak-7-day-green.ts:188
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/find-orphans.ts: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 — scripts/lean-dual-id-audit.ts:191
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/lean-migration-soak-monitor.ts:141
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/lean-readiness-check.ts:257
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/validate-contracts.ts:16
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/verify-demo-consistency.ts:20
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 — seed-notif-templates.js:17
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: DELETE /resource-pools/:id/members/:personId
`src/modules/resource-pools/presentation/resource-pools.controller.ts` declares `DELETE /resource-pools/:id/members/:personId` 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 — c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/hris/config
`src/modules/integrations/hris/presentation/hris.controller.ts` declares `GET /admin/hris/config` 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 documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/platform-settings/by-prefix/:prefix
`src/modules/platform-settings/presentation/platform-settings.controller.ts` declares `GET /admin/platform-settings/by-prefix/:prefix` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /auth/oidc/callback
`src/modules/auth/oidc.controller.ts` declares `GET /auth/oidc/callback` 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 /auth/oidc/login
`src/modules/auth/oidc.controller.ts` declares `GET /auth/oidc/login` 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/history
`src/modules/integrations-hub/presentation/integration-sync-history.controller.ts` declares `GET /integrations/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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /integrations/jira/status
`src/modules/integrations/jira/presentation/jira-integrations.controller.ts` declares `GET /integrations/jira/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 r…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /integrations/m365/directory/reconciliation
`src/modules/integrations/m365/presentation/m365-directory.controller.ts` declares `GET /integrations/m365/directory/reconciliation` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /integrations/m365/directory/status
`src/modules/integrations/m365/presentation/m365-directory.controller.ts` declares `GET /integrations/m365/directory/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 — con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /integrations/radius/reconciliation
`src/modules/integrations/radius/presentation/radius.controller.ts` declares `GET /integrations/radius/reconciliation` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /integrations/radius/status
`src/modules/integrations/radius/presentation/radius.controller.ts` declares `GET /integrations/radius/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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /notifications/outcomes
`src/modules/notifications/presentation/notifications.controller.ts` declares `GET /notifications/outcomes` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /notifications/queue
`src/modules/notifications/presentation/notifications.controller.ts` declares `GET /notifications/queue` 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 do…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /notifications/templates
`src/modules/notifications/presentation/notifications.controller.ts` declares `GET /notifications/templates` 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 o…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /project-positions/:id
`src/modules/project-positions/presentation/project-positions.controller.ts` declares `GET /project-positions/:id` 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 remo…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /project-positions/:id/candidates
`src/modules/project-positions/presentation/project-positions.controller.ts` declares `GET /project-positions/:id/candidates` 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 — co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /project-positions/:id/forensics
`src/modules/project-positions/presentation/project-positions.controller.ts` declares `GET /project-positions/:id/forensics` 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 — con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /project-positions/:id/history
`src/modules/project-positions/presentation/project-positions.controller.ts` declares `GET /project-positions/:id/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 — consi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /project-positions/:personId/suggested-positions
`src/modules/project-positions/presentation/project-positions.controller.ts` declares `GET /project-positions/:personId/suggested-positions` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /project-positions/bench
`src/modules/project-positions/presentation/project-positions.controller.ts` declares `GET /project-positions/bench` 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 re…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /resource-pools/:id
`src/modules/resource-pools/presentation/resource-pools.controller.ts` declares `GET /resource-pools/:id` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /admin/platform-settings/:key
`src/modules/platform-settings/presentation/platform-settings.controller.ts` declares `PATCH /admin/platform-settings/:key` 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 — cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /resource-pools/:id
`src/modules/resource-pools/presentation/resource-pools.controller.ts` declares `PATCH /resource-pools/:id` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/hris/config
`src/modules/integrations/hris/presentation/hris.controller.ts` declares `POST /admin/hris/config` 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 document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/hris/sync
`src/modules/integrations/hris/presentation/hris.controller.ts` declares `POST /admin/hris/sync` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/hris/test
`src/modules/integrations/hris/presentation/hris.controller.ts` declares `POST /admin/hris/test` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/login
`src/modules/auth/auth.controller.ts` declares `POST /auth/login` 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 /auth/logout
`src/modules/auth/auth.controller.ts` declares `POST /auth/logout` 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 /auth/password-reset/request
`src/modules/auth/auth.controller.ts` declares `POST /auth/password-reset/request` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/refresh
`src/modules/auth/auth.controller.ts` declares `POST /auth/refresh` 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 /integrations/jira/projects/sync
`src/modules/integrations/jira/presentation/jira-integrations.controller.ts` declares `POST /integrations/jira/projects/sync` 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 — co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /integrations/jira/reset-sync
`src/modules/integrations/jira/presentation/jira-integrations.controller.ts` declares `POST /integrations/jira/reset-sync` 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 — consi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /integrations/jira/retry-sync
`src/modules/integrations/jira/presentation/jira-integrations.controller.ts` declares `POST /integrations/jira/retry-sync` 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 — consi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /integrations/jira/test-connection
`src/modules/integrations/jira/presentation/jira-integrations.controller.ts` declares `POST /integrations/jira/test-connection` 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 — …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /integrations/m365/directory/retry-sync
`src/modules/integrations/m365/presentation/m365-directory.controller.ts` declares `POST /integrations/m365/directory/retry-sync` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /integrations/m365/directory/sync
`src/modules/integrations/m365/presentation/m365-directory.controller.ts` declares `POST /integrations/m365/directory/sync` 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 — cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /integrations/m365/directory/test-connection
`src/modules/integrations/m365/presentation/m365-directory.controller.ts` declares `POST /integrations/m365/directory/test-connection` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /integrations/radius/accounts/sync
`src/modules/integrations/radius/presentation/radius.controller.ts` declares `POST /integrations/radius/accounts/sync` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /integrations/radius/retry-sync
`src/modules/integrations/radius/presentation/radius.controller.ts` declares `POST /integrations/radius/retry-sync` 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 rem…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /integrations/radius/test-connection
`src/modules/integrations/radius/presentation/radius.controller.ts` declares `POST /integrations/radius/test-connection` 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 — conside…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /notifications/nudge
`src/modules/notifications/presentation/notifications.controller.ts` declares `POST /notifications/nudge` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /notifications/queue/:id/requeue
`src/modules/notifications/presentation/notifications.controller.ts` declares `POST /notifications/queue/:id/requeue` 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 r…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /notifications/test-send
`src/modules/notifications/presentation/notifications.controller.ts` declares `POST /notifications/test-send` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /project-positions/:id/transition
`src/modules/project-positions/presentation/project-positions.controller.ts` declares `POST /project-positions/:id/transition` 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 — c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /project-positions/bench/check
`src/modules/project-positions/presentation/project-positions.controller.ts` declares `POST /project-positions/bench/check` 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 — cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /project-positions/bulk-reassign
`src/modules/project-positions/presentation/project-positions.controller.ts` declares `POST /project-positions/bulk-reassign` 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 — co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /project-positions/create-and-book
`src/modules/project-positions/presentation/project-positions.controller.ts` declares `POST /project-positions/create-and-book` 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 — …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /resource-pools/:id/members
`src/modules/resource-pools/presentation/resource-pools.controller.ts` declares `POST /resource-pools/:id/members` 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 remo…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /staffing-requests/:id/proposals
`src/shared/config/require-feature.decorator.ts` declares `POST /staffing-requests/:id/proposals` 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 documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /undo/:id/consume
`src/modules/undo/presentation/undo.controller.ts` declares `POST /undo/:id/consume` 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 consum…
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/staffing-desk/WorkforcePlanner.tsx (1005 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/routes/dashboard/PlannedVsActualPage.tsx (872 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/routes/my-time/MyTimePage.tsx (1266 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: prisma/seed.ts (1395 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: prisma/seeds/it-company-profile.ts (2237 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/notifications/application/notification-event-translator.service.ts (1980 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/staffing-desk/application/workforce-planner.service.ts (2031 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/integration/migration-contracts.generated.spec.ts (5219 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/637cb920-111a-4c2a-a0e3-861c0db6be38/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/637cb920-111a-4c2a-a0e3-861c0db6be38/

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.