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

TUM-Dev/NavigaTUM

https://github.com/TUM-Dev/NavigaTUM · scanned 2026-06-16 00:44 UTC (2 months, 1 week ago)

39 raw signals (0 security + 39 graph)

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

Complete repo analysis

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

JSON
Combined
60.6
/100
Security checks
61
0 findings
System graph
61
100.0% cov · 34 findings
Critical
0
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 0 High 1 Medium 11 Low 12 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 34 Crowd 0 Layer: Api 1 Frontend 1 Network 1 Hardware 8 Security 5 Cicd 2 Quality 16
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 60.6/100 with 100.0% coverage. It contains 854 nodes across 1 cross-layer flows, written primarily in mixed languages. Engine surfaced 39 findings — concentrated in quality (16), hardware (8), cicd (7). Risk profile is high: 0 critical, 1 high, 16 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 24 of 34 actionable findings. 39 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.

high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: .env
`.env` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.
.env ConfigEnv fileRuntime env
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — webclient/app/composables/feedbackToken.ts:36
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 — webclient/nuxt.config.ts:77
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 — webclient/server/plugins/user-agent.ts:2
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 hardware Security conf 1.00 Dockerfile runs as root: map/martin/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: webclient/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 6 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
6 files, 6 locations
.github/workflows/_docker-build.yml
.github/workflows/ci.yaml
.github/workflows/martin-cicd.yml
.github/workflows/server-cicd.yml
.github/workflows/update-data.yml
.github/workflows/webclient-cicd.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in webclient/app/composables/FloorControl.ts:45
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
webclient/app/composables/FloorControl.ts:45 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in webclient/app/components/AddressResultContent.vue:19
Found a known-risky pattern (vue_v_html). Review and replace if possible.
webclient/app/components/AddressResultContent.vue:19 Vue v html
medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in webclient/app/components/LocationResultContent.vue:28
Found a known-risky pattern (vue_v_html). Review and replace if possible.
webclient/app/components/LocationResultContent.vue:28 Vue v html
medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in webclient/app/components/SearchFilterChips.vue:386
Found a known-risky pattern (vue_v_html). Review and replace if possible.
webclient/app/components/SearchFilterChips.vue:386 Vue v html
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.
compose.local.yml Ports
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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: alpine:3.24
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
server/Dockerfile:97 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: ghcr.io/astral-sh/uv:python3.14-bookworm
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
server/Dockerfile:5 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: ghcr.io/maplibre/martin:nightly
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
map/martin/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:24-alpine3.23
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
webclient/Dockerfile:3 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: rust:1.96-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
server/Dockerfile:38 containersPinned dependencies
low System graph quality Tests conf 1.00 Low test-to-source ratio
26 tests / 132 src (ratio 0.20).
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.
webclient/package.json CI/CD securitySupply chainNpm
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph quality Complexity conf 1.00 Very large file: motis-openapi-progenitor/src/lib.rs (12553 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: server/src/search_executor/mod.rs (1963 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: webclient/app/api_types/index.ts (3254 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/2dd365bd-e459-4aa4-a24e-6207f8dc69cc/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2dd365bd-e459-4aa4-a24e-6207f8dc69cc/

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.