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

wayweltstoregmbh/specdrift

https://github.com/wayweltstoregmbh/specdrift · scanned 2026-06-16 00:55 UTC (2 months, 1 week ago)

100 raw signals (0 security + 100 graph)

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

Complete repo analysis

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

JSON
Combined
77.7
/100
Security checks
78
0 findings
System graph
78
66.7% cov · 62 findings
Critical
5
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 5 High 0 Medium 35 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 62 Crowd 0 Layer: Frontend 19 Security 38 Quality 5
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 77.7/100 with 66.7% coverage. It contains 2760 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 100 findings — concentrated in security (76), frontend (19), quality (5). Risk profile is high: 43 critical, 0 high, 35 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 54 of 62 actionable findings. 100 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.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — validation/enterprise-evaluation/runs/run-009-ui-api-screenshot-evidence/run-ui-api-screenshot-eval.js:252
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 security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-001-secure-vendor-access/run-secure-vendor-access-eval.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-001-secure-vendor-access/run-secure-vendor-access-eval.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-002-update-preservation/run-update-preservation-eval.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-002-update-preservation/run-update-preservation-eval.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-003-open-work-handoff/run-open-work-handoff-eval.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-003-open-work-handoff/run-open-work-handoff-eval.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-004-evidence-plausibility/run-evidence-plausibility-eval.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-004-evidence-plausibility/run-evidence-plausibility-eval.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-005-evidence-gate/run-evidence-gate-eval.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-005-evidence-gate/run-evidence-gate-eval.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-006-evidence-calibration/run-evidence-calibration-eval.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-006-evidence-calibration/run-evidence-calibration-eval.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-007-subagent-mcp-productivity/run-mcp-evaluation.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-007-subagent-mcp-productivity/run-mcp-evaluation.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-008-open-work-categories/run-open-work-categories-eval.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-008-open-work-categories/run-open-work-categories-eval.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-009-ui-api-screenshot-evidence/run-ui-api-screenshot-eval.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-009-ui-api-screenshot-evidence/run-ui-api-screenshot-eval.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-010-subagent-iterative-claim-identity/run-iterative-claim-identity-eval.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-010-subagent-iterative-claim-identity/run-iterative-claim-identity-eval.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-011-subagent-multistep-claim-identity/run-stage-a.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-011-subagent-multistep-claim-identity/run-stage-a.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-011-subagent-multistep-claim-identity/run-stage-b.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-011-subagent-multistep-claim-identity/run-stage-b.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-012-subagent-four-step-rephrase-handoff/run-step-1.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-012-subagent-four-step-rephrase-handoff/run-step-1.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-012-subagent-four-step-rephrase-handoff/run-step-2.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-012-subagent-four-step-rephrase-handoff/run-step-2.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-012-subagent-four-step-rephrase-handoff/run-step-4.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-012-subagent-four-step-rephrase-handoff/run-step-4.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-013-subagent-priority-handoff/run-step-1.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-013-subagent-priority-handoff/run-step-1.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-013-subagent-priority-handoff/run-step-2.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-013-subagent-priority-handoff/run-step-2.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-013-subagent-priority-handoff/run-step-4.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-013-subagent-priority-handoff/run-step-4.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-014-subagent-mixed-work-priority/run-step-1.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-014-subagent-mixed-work-priority/run-step-1.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-017-subagent-adversarial-confirmation-blockers/run-mcp-step-1.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-017-subagent-adversarial-confirmation-blockers/run-mcp-step-1.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-017-subagent-adversarial-confirmation-blockers/run-mcp-step-2.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-017-subagent-adversarial-confirmation-blockers/run-mcp-step-2.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-017-subagent-adversarial-confirmation-blockers/run-mcp-step-3.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-017-subagent-adversarial-confirmation-blockers/run-mcp-step-3.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-017-subagent-adversarial-confirmation-blockers/run-mcp-step-4.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-017-subagent-adversarial-confirmation-blockers/run-mcp-step-4.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-1.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-1.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-2.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-2.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-3-finish.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-3-finish.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-3.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-3.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-4.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-4.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-5.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-5.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/mcp-experiments/agent-core-probe/run-agent-core-probe.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/mcp-experiments/agent-core-probe/run-agent-core-probe.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in validation/run-validation.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
validation/run-validation.js:5 Node child process
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 54 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph quality 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 — validation/ab-tests/test-01-pricing-engine/grader/probe.js:24
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 — validation/ab-tests/test-01-pricing-engine/grader/probe2.js:6
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 — validation/ab-tests/test-01-pricing-engine/grader/probe3.js:18
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 — validation/ab-tests/test-02-profile-validation/grader/probe.js: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 — validation/ab-tests/test-02-profile-validation/grader/run2.js:7
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 — validation/ab-tests/test-02-profile-validation/grader/run3.js:8
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 — validation/ab-tests/test-03-handoff/grader/assert.js:179
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 — validation/ab-tests/test-03-handoff/grader/diverge.js:5
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 — validation/ab-tests/test-03-handoff/grader/edge.js:56
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 — validation/ab-tests/test-03-handoff/grader/probe.js:173
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 — validation/enterprise-evaluation/runs/run-001-secure-vendor-access/project/tests/run-functional-tests.js:77
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 — validation/enterprise-evaluation/runs/run-001-secure-vendor-access/run-secure-vendor-access-eval.js:325
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 — validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-1.js:267
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 — validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-2.js:221
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 — validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-3-finish.js:285
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 — validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-3.js:127
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 — validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-4.js:343
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 — validation/enterprise-evaluation/runs/run-018-subagent-stale-corruption-blockers/run-step-5.js:247
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
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/ef338be1-1bab-47fa-a371-5e1fedfc6132/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ef338be1-1bab-47fa-a371-5e1fedfc6132/

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.