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.

JochenWeerda/VALEO-NeuroERP-3.0

https://github.com/JochenWeerda/VALEO-NeuroERP-3.0 · scanned 2026-06-16 04:29 UTC (2 months ago)

25 raw signals (0 security + 25 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 24 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 3 Medium 13 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 24 Crowd 0 Layer: Network 1 Hardware 1 Security 12 Cicd 1 Quality 9

Exclude dismissed / FP Exclude test files

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 73.9/100 with 100.0% coverage. It contains 341 nodes across 8 cross-layer flows, written primarily in mixed languages. Engine surfaced 25 findings — concentrated in security (12), quality (9), hardware (2). Risk profile is high: 1 critical, 3 high, 13 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 24 of 24 actionable findings. 25 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 System graph security Secrets conf 1.00 Runtime dotenv file present in repo: .env.swarm

`.env.swarm` looks like a runtime dotenv file. It contains secret-looking assignments for NEUROERP_PASS. Move real values to a secret manager and keep only `.env.example` style templates in source control.

.env.swarm ConfigEnv fileRuntime env

high System graph security auth conf 1.00 FastAPI POST `mcp_copilot_forecast_stub` without auth dependency — main.py:459

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

main.py:459 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `mcp_kpis_stub` without auth dependency — main.py:449

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

main.py:449 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `mcp_trends_stub` without auth dependency — main.py:454

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

main.py:454 securityAuth fastapi unauth mutation

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .continuerc.json

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.

.continuerc.json VerificationAgent instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md

CLAUDE.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing 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 security security conf 1.00 Insecure pattern 'cors_wildcard' in main.py:221

Found a known-risky pattern (cors_wildcard). Review and replace if possible.

main.py:221 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in .coderabbit.yaml:71

Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.

.coderabbit.yaml:71 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in lint-results.json:5

Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.

lint-results.json:5 Local storage auth token

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in playwright.global-setup.mjs:1

Found a known-risky pattern (node_child_process). Review and replace if possible.

playwright.global-setup.mjs:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in playwright.global-setup.ts:1

Found a known-risky pattern (node_child_process). Review and replace if possible.

playwright.global-setup.ts:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in playwright.global-teardown.mjs:1

Found a known-risky pattern (node_child_process). Review and replace if possible.

playwright.global-teardown.mjs:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in setup-storybook.mjs:12

Found a known-risky pattern (node_child_process). Review and replace if possible.

setup-storybook.mjs:12 Node child process

medium System graph network Security conf 1.00 Privileged port 1000 in use

Port 1000 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

Dockerfile Ports

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

3 test file(s) for 33 source file(s) (ratio 0.09). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Integrity conf 1.00 8 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `CI`, `FRONTEND_URL`, `NEUROERP_URL`, `PLAYWRIGHT_FORCE_SPAWN`, `PLAYWRIGHT_FRONTEND_PROBE_MS`, `PLAYWRIGHT_PREVIEW_PORT`, `PLAYWRIGHT_SSE_URL`, `VALEO_BASE_URL`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 794 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: python:3.11-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 3, 21

Dockerfile:3, 21 (2 hits)

containersPinned dependencies

low System graph security security conf 1.00 Insecure pattern 'document_write' in .coderabbit.yaml:71

Found a known-risky pattern (document_write). Review and replace if possible.

.coderabbit.yaml:71 Document write

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `policies_v1` in main.py:23

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts

preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.

package.json CI/CD securitySupply chainNpm

low System graph quality Complexity conf 1.00 Very large file: tmp_lieferschein_head.tsx (2523 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/3faf27b9-8a9d-473e-a35d-a220a3d11f98/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3faf27b9-8a9d-473e-a35d-a220a3d11f98/

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.