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

tornidomaroc-web/fixor

https://github.com/tornidomaroc-web/fixor · scanned 2026-06-16 00:40 UTC (2 months, 1 week ago)

290 raw signals (86 security + 204 graph)

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

Complete repo analysis

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

JSON
Combined
43.2
/100
Security checks
43
7 findings
System graph
43
100.0% cov · 198 findings
Critical
7
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 7 High 12 Medium 20 Low 92 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 198 Crowd 0 Layer: Quality 93 Security 15 Software 4 Frontend 34 Hardware 2 Cicd 2 Api 55
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 43.2/100 with 100.0% coverage. It contains 1635 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 204 findings — concentrated in quality (90), api (55), frontend (34). Risk profile is high: 5 critical, 9 high, 18 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 131 of 205 actionable findings. 396 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 15 occurrences Foundry mined mock as real or placeholder: tornidomaroc-web/fixor
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…
15 occurrences
repo-level (15 hits)
critical Security checks security auth conf 0.78 23 occurrences Foundry mined security auth guardrail gaps: tornidomaroc-web/fixor
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…
23 occurrences
repo-level (23 hits)
critical System graph security security conf 1.00 Insecure pattern 'private_key_in_repo' in fixtures/secrets-exposure/positive/03-firebase-admin-in-component.tsx:13
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
fixtures/secrets-exposure/positive/03-firebase-admin-in-component.tsx:13 Private key in repo
critical System graph security Secrets conf 1.00 Possible secret in fixtures/secrets-exposure/positive/03-firebase-admin-in-component.tsx
Detected pattern matching private_key. Rotate the credential and move to a secret manager.
fixtures/secrets-exposure/positive/03-firebase-admin-in-component.tsx:12
critical System graph security Secrets conf 1.00 Possible secret in fixtures/secrets-exposure/positive/06-aws-keys-hardcoded.js
Detected pattern matching aws_secret. Rotate the credential and move to a secret manager.
fixtures/secrets-exposure/positive/06-aws-keys-hardcoded.js:6
critical System graph security Secrets conf 1.00 Possible secret in fixtures/secrets-exposure/positive/08-postgres-password-client.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
fixtures/secrets-exposure/positive/08-postgres-password-client.ts:8
critical System graph security Secrets conf 1.00 Possible secret in src/analysis-engine/detectors/secrets-exposure.detector.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
src/analysis-engine/detectors/secrets-exposure.detector.ts:188
high Security checks quality Practices conf 0.84 14 occurrences Foundry mined bad chains: tornidomaroc-web/fixor
Comment chain pattern product: bad_chains Repo: tornidomaroc-web/fixor Thread: tornidomaroc-web/fixor#7 Outcome: ambiguous_needs_more_evidence Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_g…
14 occurrences
repo-level (14 hits)
high Security checks quality Quality conf 0.76 2 occurrences Foundry mined schema ui api mismatch: tornidomaroc-web/fixor
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_verification_signal Repo…
2 occurrences
repo-level (2 hits)
high Security checks quality Testing conf 0.78 55 occurrences Foundry mined test ci gap after feedback: tornidomaroc-web/fixor
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: weak_supervision_needs_…
55 occurrences
repo-level (55 hits)
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/user/installations (apps/dashboard/src/lib/github.ts:83)
`apps/dashboard/src/lib/github.ts:83` calls `GET https://api.github.com/user/installations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/user/installations` If this points at an external API,…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/orgs/${orgId}/settings (apps/dashboard/src/components/settings-form.tsx:58)
`apps/dashboard/src/components/settings-form.tsx:58` calls `PATCH /api/orgs/${orgId}/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/orgs/<p>/settings` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/billing/checkout (apps/dashboard/src/components/upgrade-button.tsx:40)
`apps/dashboard/src/components/upgrade-button.tsx:40` calls `POST /api/billing/checkout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/checkout` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/billing/portal (apps/dashboard/src/components/manage-subscription-buttons.tsx:30)
`apps/dashboard/src/components/manage-subscription-buttons.tsx:30` calls `POST /api/billing/portal` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/portal` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.github.com/app/installations/${installationId}/access_tokens (src/integrations/github/app-auth.service.ts:71)
`src/integrations/github/app-auth.service.ts:71` calls `POST https://api.github.com/app/installations/${installationId}/access_tokens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/app/install…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `delete_user` without auth dependency — fixtures/auth-bypass/positive/20-fastapi-bare-delete-getdb.py:11
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
fixtures/auth-bypass/positive/20-fastapi-bare-delete-getdb.py:11 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `delete_post` without auth dependency — fixtures/auth-bypass/negative/23-flask-shorthand-login-required.py:10
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
fixtures/auth-bypass/negative/23-flask-shorthand-login-required.py:10 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `delete_team` without auth dependency — fixtures/auth-bypass/negative/21-fastapi-security-current-user.py:11
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
fixtures/auth-bypass/negative/21-fastapi-security-current-user.py:11 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `update_tier` without auth dependency — fixtures/auth-bypass/positive/21-fastapi-noauth-tier-change.py:9
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
fixtures/auth-bypass/positive/21-fastapi-noauth-tier-change.py:9 securityAuth fastapi unauth mutation
medium Security checks quality Practices conf 0.62 26 occurrences Foundry mined assumption checks: tornidomaroc-web/fixor
Comment chain pattern product: assumption_checks Repo: tornidomaroc-web/fixor Thread: tornidomaroc-web/fixor#9 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_artifacts, sou…
26 occurrences
repo-level (26 hits)
medium Security checks quality maintenance conf 0.70 57 occurrences Foundry mined blueprint gap alignment: tornidomaroc-web/fixor
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: …
57 occurrences
repo-level (57 hits)
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/analysis-engine/detector.types.ts:37
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/services/xss-fix.service.ts:36
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/test/test-xss-fix.ts:74
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 — apps/dashboard/src/components/settings-form.tsx:58
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 — apps/dashboard/src/lib/paddle.ts:89
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/analysis-engine/anthropic-client.ts:9
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/analysis-engine/detectors/idor.detector.ts:241
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/integrations/github/app-auth.service.ts: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 — src/integrations/github/github-client.ts:86
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 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 cicd CI/CD security conf 1.00 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.
.github/workflows/pages.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/services/xss-fix.service.ts:36
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/services/xss-fix.service.ts:36 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/services/xss-fix.service.ts:31
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/services/xss-fix.service.ts:31 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/config/vulnerability-registry.ts:75
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/config/vulnerability-registry.ts:75 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/cmdi-fix.service.ts:34
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/cmdi-fix.service.ts:34 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/secrets_scan.py:41
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 15 placeholder/mock markers across 10 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Integrity conf 1.00 67 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ALLOW_UNSIGNED_WEBHOOKS`, `APP_VERSION`, `AWS_ACCESS_KEY_ID`, `AWS_REGION`, `AWS_SECRET_ACCESS_KEY`, `DEMO_LIVE_CONFIRM`, `DEMO_OWNER`, `DEMO_PR` + 59 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 87 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 2 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, 8
Dockerfile:1, 8 (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@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 3 locations
.github/workflows/ci.yml:23, 26 (2 hits)
.github/workflows/pages.yml:36
CI/CD securitySupply chainGithub actions
low System graph security security conf 1.00 Insecure pattern 'document_write' in src/services/xss-fix.service.ts:40
Found a known-risky pattern (document_write). Review and replace if possible.
src/services/xss-fix.service.ts:40 Document write
low System graph quality Tests conf 1.00 Low test-to-source ratio
54 tests / 331 src (ratio 0.16).
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: fixtures/idor/positive/03-fastapi.py:get_invoice, fixtures/idor/positive/03-fastapi.py:void_invoice This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're…
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph software Dead code conf 1.00 Possibly dead Python function: daily_revenue_report
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
fixtures/secrets-exposure/negative/09-slack-webhook-from-env.py:18
low System graph software Dead code conf 1.00 Possibly dead Python function: daily_revenue_report
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
fixtures/secrets-exposure/positive/09-slack-webhook-hardcoded.py:21
low System graph software Dead code conf 1.00 Possibly dead Python function: require_admin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
fixtures/admin-check/negative/09-fastapi-rbac-dep.py:10
low System graph software Dead code conf 1.00 Possibly dead Python function: require_auth
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
fixtures/auth-bypass/positive/08-jwt-verify-false.py:9
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 — fixtures/admin-check/negative/18-remix-action-factory-utility-module.ts:19
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 — fixtures/auth-bypass/negative/19-remix-loader-factory-utility-module.ts:22
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 — src/demo/real-github-demo.ts:61
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 — src/integrations/github/demo/run-pr-webhook-dry-run.ts:67
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 — src/integrations/github/demo/validate-github-comment-demo.ts:158
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 — src/real-tests/run-real-tests.ts:182
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 — src/scripts/create-api-token.ts:71
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 — src/scripts/migrate-json-ledger-to-pg.ts:58
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 — src/test/run-fixture-tests.ts:157
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 — src/test/test-anthropic-retry.ts:183
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 — src/test/test-cmdi-fix.ts:150
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 — src/test/test-cost-tracking.ts:96
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 — src/test/test-degraded-coverage.ts:58
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 — src/test/test-diff-parser.ts:35
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 — src/test/test-exploit-generator.ts:25
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 — src/test/test-file-walker.ts:217
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 — src/test/test-full-comment.ts:83
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 — src/test/test-llm-fix.ts:22
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 — src/test/test-org-settings-filter.ts:219
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 — src/test/test-pr-diff-analyzer.ts:23
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 — src/test/test-pt-fix.ts:92
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 — src/test/test-rate-limiter.ts:94
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 — src/test/test-real-shape-reachability.ts:64
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 — src/test/test-sarif-output.ts:129
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 — src/test/test-scan-limit-warning.ts:163
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 — src/test/test-whole-file-input.ts:49
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 — src/test/test-xss-fix.ts:168
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 — src/test/validate-e2e.ts:64
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 — src/workflows/test-harness.ts:30
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: ANY /account/delete
`fixtures/auth-bypass/negative/22-flask-login-required.py` declares `ANY /account/delete` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin/users/<int:user_id>
`fixtures/admin-check/negative/21-flask-admin-required.py` declares `ANY /admin/users/<int:user_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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /users/<int:user_id>
`fixtures/auth-bypass/positive/22-flask-bare-route-no-auth.py` declares `ANY /users/<int:user_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 document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:id
`fixtures/real-shape/express-saas/src/routes/accounts.js` declares `DELETE /: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 documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /account
`fixtures/auth-bypass/negative/20-fastapi-depends-current-user.py` declares `DELETE /account` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/notes/<int:note_id>
`fixtures/auth-bypass/positive/07-flask-anon-skip.py` declares `DELETE /api/notes/<int:note_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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/users/:id
`fixtures/admin-check/negative/05-db-role-on-delete.js` declares `DELETE /api/users/: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 documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/users/<user_id>
`fixtures/admin-check/negative/08-flask-db-role.py` declares `DELETE /api/users/<user_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 documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /users/{user_id}
`fixtures/auth-bypass/positive/20-fastapi-bare-delete-getdb.py` declares `DELETE /users/{user_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 document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /{item_id}
`fixtures/real-shape/fastapi-saas/app/routers/items.py` declares `DELETE /{item_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 documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /{user_id}
`fixtures/real-shape/fastapi-saas/app/routers/users.py` declares `DELETE /{user_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 documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`fixtures/real-shape/fastapi-saas/app/routers/items.py` declares `GET /` 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 /:id
`fixtures/real-shape/express-saas/src/routes/documents.js` declares `GET /: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 documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/dashboard
`fixtures/admin-check/negative/09-fastapi-rbac-dep.py` declares `GET /admin/dashboard` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/stats
`fixtures/real-shape/fastapi-saas/app/routers/admin.py` declares `GET /admin/stats` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/customers/:id
`fixtures/env-exposure/positive/07-error-includes-env.js` declares `GET /api/customers/: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 documenting who…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/diagnostics
`fixtures/env-exposure/positive/08-flask-diagnostics.py` declares `GET /api/diagnostics` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/homepage
`fixtures/auth-bypass/negative/06-flask-anon-static.py` declares `GET /api/homepage` 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 api Wiring conf 1.00 Unused endpoint: GET /api/v1/diagnostics
`fixtures/env-exposure/positive/11-redacted-diagnostics.js` declares `GET /api/v1/diagnostics` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/health
`fixtures/env-exposure/negative/06-logger-only-env.js` declares `GET /api/v1/health` 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 api Wiring conf 1.00 Unused endpoint: GET /internal/env-keys
`fixtures/env-exposure/negative/08-flask-env-keys-only.py` declares `GET /internal/env-keys` 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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /internal/runtime
`fixtures/env-exposure/negative/09-fastapi-runtime-specific.py` declares `GET /internal/runtime` 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: GET /invoices
`fixtures/auth-bypass/positive/05-missing-middleware.js` declares `GET /invoices` 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: GET /me
`fixtures/real-shape/fastapi-saas/app/routers/users.py` declares `GET /me` 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 /stats
`fixtures/admin-check/positive/20-fastapi-admin-stats-no-gate.py` declares `GET /stats` 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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /subscription
`fixtures/auth-bypass/positive/05-missing-middleware.js` declares `GET /subscription` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /teams
`fixtures/auth-bypass/negative/11-router-properly-guarded.ts` declares `GET /teams` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{doc_id}
`fixtures/idor/negative/09-fastapi-ownership-check.py` declares `GET /{doc_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 documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{invoice_id}
`fixtures/idor/positive/03-fastapi.py` declares `GET /{invoice_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 documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{item_id}
`fixtures/real-shape/fastapi-saas/app/routers/items.py` declares `GET /{item_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 documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{report_id}
`fixtures/idor-tenant/negative/03-fastapi-sqlalchemy-postfetch.py` declares `GET /{report_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 documenting …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /me
`fixtures/real-shape/fastapi-saas/app/routers/users.py` declares `PATCH /me` 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 /:id/role
`fixtures/real-shape/express-saas/src/routes/admin.js` declares `POST /:id/role` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/users/{user_id}/role
`fixtures/real-shape/fastapi-saas/app/routers/admin.py` declares `POST /admin/users/{user_id}/role` 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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/admin/promote
`fixtures/admin-check/negative/06-claims-middleware.js` declares `POST /api/admin/promote` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /billing/tier
`fixtures/auth-bypass/positive/21-fastapi-noauth-tier-change.py` declares `POST /billing/tier` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /cancel
`fixtures/auth-bypass/positive/05-missing-middleware.js` declares `POST /cancel` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /posts/<int:post_id>/delete
`fixtures/auth-bypass/negative/23-flask-shorthand-login-required.py` declares `POST /posts/<int:post_id>/delete` 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 removi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /teams/:id/delete
`fixtures/auth-bypass/negative/11-router-properly-guarded.ts` declares `POST /teams/:id/delete` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /teams/:id/rename
`fixtures/auth-bypass/negative/11-router-properly-guarded.ts` declares `POST /teams/:id/rename` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /teams/{team_id}/delete
`fixtures/auth-bypass/negative/21-fastapi-security-current-user.py` declares `POST /teams/{team_id}/delete` 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 /users/:id/role
`fixtures/real-shape/lane-boundary/express-admin-no-auth.js` declares `POST /users/:id/role` 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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /users/{user_id}/promote
`fixtures/admin-check/negative/20-fastapi-superuser-inline.py` declares `POST /users/{user_id}/promote` 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 doc…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /users/{user_id}/role
`fixtures/real-shape/lane-boundary/fastapi-admin-no-auth.py` declares `POST /users/{user_id}/role` 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 /webhook/github
`fixtures/webhook-unverified/negative/08-flask-github-compare-digest.py` declares `POST /webhook/github` 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: POST /webhook/lemon
`fixtures/webhook-unverified/positive/05-lemon-no-sig.js` declares `POST /webhook/lemon` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /webhook/stripe
`fixtures/webhook-unverified/negative/07-flask-stripe-construct-event.py` declares `POST /webhook/stripe` 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 /webhook/twilio/sms
`fixtures/webhook-unverified/negative/06-twilio-validate-request.js` declares `POST /webhook/twilio/sms` 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: POST /webhook/usage
`fixtures/webhook-unverified/negative/03-custom-strict-hmac.ts` declares `POST /webhook/usage` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{invoice_id}/void
`fixtures/idor/positive/03-fastapi.py` declares `POST /{invoice_id}/void` 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
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/01bde0d6-b133-467f-9e4b-0e98b55e7156/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/01bde0d6-b133-467f-9e4b-0e98b55e7156/

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.