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

selhorys/dataspoke-baseline

https://github.com/selhorys/dataspoke-baseline · scanned 2026-06-16 00:06 UTC (2 months, 2 weeks ago)

227 raw signals (9 security + 218 graph)

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

Complete repo analysis

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

JSON
Combined
56.8
/100
Security checks
57
8 findings
System graph
57
100.0% cov · 197 findings
Critical
3
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 3 High 28 Medium 18 Low 91 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 197 Crowd 0 Layer: Quality 103 Security 28 Software 8 Frontend 8 Hardware 7 Cicd 1 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 56.8/100 with 100.0% coverage. It contains 5094 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 218 findings — concentrated in quality (114), api (50), security (28). Risk profile is high: 2 critical, 25 high, 15 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 138 of 205 actionable findings. 381 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 28 occurrences Foundry mined mock as real or placeholder: selhorys/dataspoke-baseline
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…
28 occurrences
repo-level (28 hits)
critical Security checks security auth conf 0.78 Foundry mined security auth guardrail gaps: selhorys/dataspoke-baseline
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…
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in src/api/routers/admin.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 507, 747
src/api/routers/admin.py:507, 747 (2 hits)
high Security checks quality Practices conf 0.84 53 occurrences Foundry mined bad chains: selhorys/dataspoke-baseline
Comment chain pattern product: bad_chains Repo: selhorys/dataspoke-baseline Thread: selhorys/dataspoke-baseline#9 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifa…
53 occurrences
repo-level (53 hits)
high Security checks quality Quality conf 0.76 2 occurrences Foundry mined schema ui api mismatch: selhorys/dataspoke-baseline
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: needs_more_evidence Repo: selhorys/da…
2 occurrences
repo-level (2 hits)
high Security checks quality Testing conf 0.78 15 occurrences Foundry mined test ci gap after feedback: selhorys/dataspoke-baseline
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: needs_more_evidence Rep…
15 occurrences
repo-level (15 hits)
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/skills/datahub-api/SKILL.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/skills/datahub-api/SKILL.md:121 SecretsClaude instruction
high System graph security auth conf 1.00 FastAPI DELETE `delete_user_api_token` without auth dependency — src/api/routers/admin.py:705
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/admin.py:705 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_user` without auth dependency — src/api/routers/admin.py:666
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/admin.py:666 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_conf` without auth dependency — src/api/routers/admin.py:240
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/admin.py:240 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_datahub_peripheral` without auth dependency — src/api/routers/admin.py:391
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/admin.py:391 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_langfuse_peripheral` without auth dependency — src/api/routers/admin.py:458
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/admin.py:458 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_smtp_peripheral` without auth dependency — src/api/routers/admin.py:555
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/admin.py:555 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_user_role` without auth dependency — src/api/routers/admin.py:644
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/admin.py:644 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_user` without auth dependency — src/api/routers/admin.py:622
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/admin.py:622 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `auth_role_sync` without auth dependency — src/api/routers/internal/activities.py:328
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/internal/activities.py:328 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingestion_list_active` without auth dependency — src/api/routers/internal/activities.py:73
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/internal/activities.py:73 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingestion_run` without auth dependency — src/api/routers/internal/activities.py:93
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/internal/activities.py:93 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingestion_sync` without auth dependency — src/api/routers/internal/activities.py:118
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/internal/activities.py:118 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `metagen_run` without auth dependency — src/api/routers/internal/activities.py:154
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/internal/activities.py:154 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `metrics_list_active` without auth dependency — src/api/routers/internal/activities.py:206
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/internal/activities.py:206 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `metrics_run` without auth dependency — src/api/routers/internal/activities.py:235
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/internal/activities.py:235 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ontogen_run` without auth dependency — src/api/routers/internal/activities.py:272
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/internal/activities.py:272 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_password_reset_confirm` without auth dependency — src/api/routers/auth.py:293
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/auth.py:293 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_password_reset_request` without auth dependency — src/api/routers/auth.py:280
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/auth.py:280 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_register` without auth dependency — src/api/routers/auth.py:109
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/auth.py:109 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_token_refresh` without auth dependency — src/api/routers/auth.py:183
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/auth.py:183 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_token_revoke` without auth dependency — src/api/routers/auth.py:222
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/auth.py:222 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_token` without auth dependency — src/api/routers/auth.py:156
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/auth.py:156 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `verify_dags` without auth dependency — src/api/routers/admin.py:99
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routers/admin.py:99 securityAuth fastapi unauth mutation
medium Security checks quality Practices conf 0.62 2 occurrences Foundry mined assumption checks: selhorys/dataspoke-baseline
Comment chain pattern product: assumption_checks Repo: selhorys/dataspoke-baseline Thread: selhorys/dataspoke-baseline#36 Outcome: ambiguous_needs_more_evidence Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_re…
2 occurrences
repo-level (2 hits)
medium Security checks quality Practices conf 0.72 16 occurrences Foundry mined review feedback without structured fix: selhorys/dataspoke-baseline
Graph query export: Review feedback without structured fix chain Query id: review_feedback_without_structured_fix Query type: motif_query Intent: Weak-supervision examples for review comments lacking a traceable fix. Motif: review_feedback_without_structured_fix Training usage: weak_supervision Gra…
16 occurrences
repo-level (16 hits)
medium Security checks quality Practices conf 0.70 46 occurrences Foundry mined unresolved feedback: selhorys/dataspoke-baseline
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…
46 occurrences
repo-level (46 hits)
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/frontend/app/layout.tsx:52
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/frontend/lib/api/client.ts:139
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/agent-memory/reviewer/feedback_bash_errexit_grep_output.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/agent-memory/reviewer/feedback_bash_errexit_grep_output.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/agent-memory/reviewer/MEMORY.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/agent-memory/reviewer/MEMORY.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/k8s-work/reference.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/k8s-work/reference.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/k8s-work/troubleshooting.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/k8s-work/troubleshooting.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/prauto-check-status/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/prauto-check-status/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing ci. 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: docker-images/airflow/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: docker-images/api/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/frontend/app/layout.tsx:52
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/frontend/app/layout.tsx:52 Dangerous innerhtml
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 54 placeholder/mock markers across 32 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 16 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `DATASPOKE_AIRFLOW_URL`, `DATASPOKE_ALEMBIC_URL`, `DATASPOKE_API_BASE_URL`, `DATASPOKE_DATAHUB_URL`, `DATASPOKE_EMBEDDING_API_KEY`, `DATASPOKE_INTERNAL_TOKEN`, `DATASPOKE_LANGFUSE_URL`, `DATASPOKE_POSTGRES_DB` + 8 more. Add them (with a placeholder…
config drift
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: apache/airflow:3.1.8-python3.13
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker-images/airflow/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: bitnamilegacy/postgresql:17.6.0-debian-12-r4
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker-images/postgres/Dockerfile:69 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:22-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 2, 17
src/frontend/Dockerfile:2, 17 (2 hits)
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: postgres:17-bookworm
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker-images/postgres/Dockerfile:27 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.13-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 2, 12
docker-images/api/Dockerfile:2, 12 (2 hits)
containersPinned dependencies
low System graph quality Integrity conf 1.00 18 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: src/api/schemas/metrics.py:validate_fields, src/api/schemas/metrics.py:validate_fields 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 separate.
18 occurrences
repo-level (18 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: src/workflows/dags/metrics_weekly.py:extract_targets, src/workflows/dags/metrics_daily.py:extract_targets, src/workflows/dags/metrics_hourly.py:extract_targets This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https:/…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `auto_browse_path_v2` in tests/integration/util/datahub.py:910
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 `cert_v2` in tests/unit/shared/secrets/test_grammar.py: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 `existing_v2` in tests/unit/backend/admin/test_config_service.py:405
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 `idx_old` in tests/unit/shared/datahub/test_consumer_reconfig.py:395
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 `MetadataChangeLog_Versioned_v1` in src/shared/datahub/consumer.py: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 `MetadataChangeLog_Versioned_v1` in tests/unit/shared/datahub/test_consumer.py:12
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 `order_line_v1` in tests/unit/backend/ontogen/test_validator.py:167
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 `secret_v1` in tests/unit/backend/admin/test_datahub_secret.py:405
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 `secret_v1` in tests/unit/backend/admin/test_langfuse_secret.py:397
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 `secret_v1` in tests/unit/backend/admin/test_llm_secret.py:487
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 software Dead code conf 1.00 Possibly dead Python function: decorator
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/backend/metrics/measurers/registry.py:31
low System graph software Dead code conf 1.00 Possibly dead Python function: ensure_collection
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/shared/vector/client.py:57
low System graph software Dead code conf 1.00 Possibly dead Python function: ensure_collection
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/workflows/_stubs.py:195
low System graph software Dead code conf 1.00 Possibly dead Python function: invalidate_oauth_client
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/backend/auth/oauth_google.py:78
low System graph software Dead code conf 1.00 Possibly dead Python function: make_metagen
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/workflows/_common.py:201
low System graph software Dead code conf 1.00 Possibly dead Python function: make_ontogen
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/workflows/_common.py:179
low System graph software Dead code conf 1.00 Possibly dead Python function: schema_pred
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/shared/models/ingestion.py:265
low System graph software Dead code conf 1.00 Possibly dead Python function: schema_table_pred
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/shared/models/ingestion.py:273
low System graph frontend Frontend quality conf 1.00 React Flow edge with `label=` but no project-wide edge-label CSS override — src/frontend/lib/ontogen-triple-gate.ts:84
React Flow edge labels render with a white rectangle behind the text by default, which scatters bright boxes across a dark canvas. Either drop the label, or override `.react-flow__edge-textbg` and `.react-flow__edge-text` in your stylesheet. Why: P-H in CHECKLIST.md — vendor edge labels bleed whit…
Fq edge label no bg
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 — tests/e2e/global-setup.ts:54
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 — tests/e2e/global-teardown.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 quality Integrity conf 1.00 Stub function `ensure_collection` (body is just `pass`/`return`) — src/workflows/_stubs.py:195
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: ANY /openapi/{path:path}
`src/api/routers/hub.py` declares `ANY /openapi/{path:path}` 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: DELETE /api-tokens/{token_id}
`src/api/routers/auth.py` declares `DELETE /api-tokens/{token_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: DELETE /attr/conf
`src/api/routers/spoke/metagen.py` declares `DELETE /attr/conf` 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: DELETE /users/{user_id}
`src/api/routers/admin.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 documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /users/{user_id}/api-tokens/{token_id}
`src/api/routers/admin.py` declares `DELETE /users/{user_id}/api-tokens/{token_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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /{metric_id}/attr/conf
`src/api/routers/spoke/governance.py` declares `DELETE /{metric_id}/attr/conf` 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 /
`src/api/routers/spoke/governance.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 /api-tokens
`src/api/routers/auth.py` declares `GET /api-tokens` 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 /attr/conf
`src/api/routers/spoke/metagen.py` declares `GET /attr/conf` 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 /conf
`src/api/routers/admin.py` declares `GET /conf` 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 /event
`src/api/routers/spoke/metagen.py` declares `GET /event` 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 /google/callback
`src/api/routers/auth.py` declares `GET /google/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 /google/login
`src/api/routers/auth.py` declares `GET /google/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 /item
`src/api/routers/spoke/metagen.py` declares `GET /item` 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/{composite_id:path}
`src/api/routers/spoke/metagen.py` declares `GET /item/{composite_id:path}` 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 /me
`src/api/routers/auth.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 /peripherals
`src/api/routers/admin.py` declares `GET /peripherals` 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 /peripherals/datahub
`src/api/routers/admin.py` declares `GET /peripherals/datahub` 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 /peripherals/langfuse
`src/api/routers/admin.py` declares `GET /peripherals/langfuse` 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 /peripherals/smtp
`src/api/routers/admin.py` declares `GET /peripherals/smtp` 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 /ready
`src/api/routers/health.py` declares `GET /ready` 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 /users
`src/api/routers/admin.py` declares `GET /users` 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 /users/{user_id}/api-tokens
`src/api/routers/admin.py` declares `GET /users/{user_id}/api-tokens` 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 /{metric_id}
`src/api/routers/spoke/governance.py` declares `GET /{metric_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 /{metric_id}/attr
`src/api/routers/spoke/governance.py` declares `GET /{metric_id}/attr` 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 /{metric_id}/attr/conf
`src/api/routers/spoke/governance.py` declares `GET /{metric_id}/attr/conf` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /attr/conf
`src/api/routers/spoke/metagen.py` declares `PATCH /attr/conf` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /conf
`src/api/routers/admin.py` declares `PATCH /conf` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /me
`src/api/routers/auth.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: PATCH /peripherals/datahub
`src/api/routers/admin.py` declares `PATCH /peripherals/datahub` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /peripherals/langfuse
`src/api/routers/admin.py` declares `PATCH /peripherals/langfuse` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /peripherals/smtp
`src/api/routers/admin.py` declares `PATCH /peripherals/smtp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /users/{user_id}
`src/api/routers/admin.py` declares `PATCH /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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /users/{user_id}/role
`src/api/routers/admin.py` declares `PATCH /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 documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /{metric_id}/attr/conf
`src/api/routers/spoke/governance.py` declares `PATCH /{metric_id}/attr/conf` 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 /
`src/api/routers/spoke/governance.py` declares `POST /` 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 /api-tokens
`src/api/routers/auth.py` declares `POST /api-tokens` 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 /bootstrap
`src/api/routers/admin.py` declares `POST /bootstrap` 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 /dags/verify
`src/api/routers/admin.py` declares `POST /dags/verify` 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 /datahub/sync
`src/api/routers/admin.py` declares `POST /datahub/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 documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /graphql
`src/api/routers/hub.py` declares `POST /graphql` 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 /method/run
`src/api/routers/spoke/metagen.py` declares `POST /method/run` 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 /password/reset/confirm
`src/api/routers/auth.py` declares `POST /password/reset/confirm` 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 /password/reset/request
`src/api/routers/auth.py` declares `POST /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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /register
`src/api/routers/auth.py` declares `POST /register` 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 /token
`src/api/routers/auth.py` declares `POST /token` 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 /token/refresh
`src/api/routers/auth.py` declares `POST /token/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 /token/revoke
`src/api/routers/auth.py` declares `POST /token/revoke` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /attr/conf
`src/api/routers/spoke/metagen.py` declares `PUT /attr/conf` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /{metric_id}/attr/conf
`src/api/routers/spoke/governance.py` declares `PUT /{metric_id}/attr/conf` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: src/backend/ingestion/service.py (1536 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/backend/metagen/service.py (1386 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/backend/ontogen/service.py (1767 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/e2e/use-case/uc4-01-metadata-generation.spec.ts (1431 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/integration/api_wired/test_uc1_01_datahub_managed.py (1058 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/integration/api_wired/test_uc4_01_metadata_generation.py (1627 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/integration/spot/test_metrics.py (2053 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/unit/backend/metagen/test_service.py (2038 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/unit/backend/ontogen/test_service.py (1296 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/unit/backend/ontogen/test_validator.py (1429 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/b404da01-70b3-49aa-96e1-2a2006063a1e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/b404da01-70b3-49aa-96e1-2a2006063a1e/

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.