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

raddatzk/veyq

https://github.com/raddatzk/veyq · scanned 2026-06-15 23:46 UTC (2 months, 4 weeks ago)

133 raw signals (44 security + 89 graph)

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

Complete repo analysis

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

JSON
Combined
57.8
/100
Security checks
58
8 findings
System graph
58
100.0% cov · 41 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 3 Medium 17 Low 22 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 41 Crowd 0 Layer: Quality 20 Security 9 Cicd 5 Software 3 Api 1 Hardware 11
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 57.8/100 with 100.0% coverage. It contains 3032 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 89 findings — concentrated in cicd (37), security (21), quality (14). Risk profile is high: 16 critical, 0 high, 31 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 45 of 49 actionable findings. 199 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 cicd CI/CD security conf 0.86 17 occurrences Foundry mined claimed resolved with failing ci: raddatzk/veyq
Graph query export: Claimed resolved with failing CI Query id: claimed_resolved_with_failing_ci Query type: motif_query Intent: Hard negatives where CI/failure evidence contradicts a resolution claim. Motif: claimed_resolved_with_failing_ci Training usage: hard_negative Graph gold label: contradict…
17 occurrences
repo-level (17 hits)
CI/CD securityCI/CD
critical Security checks security auth conf 0.78 6 occurrences Foundry mined security auth guardrail gaps: raddatzk/veyq
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…
6 occurrences
repo-level (6 hits)
critical System graph security Secrets conf 1.00 14 occurrences Possible secret in frontend/src/i18n/messages.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 19, 43, 64, 100, 524, 534, 753, 1099, +6 more
frontend/src/i18n/messages.ts:19, 43, 64, 100, 524, 534, 753, 1099, +6 more (14 hits)
critical System graph security Secrets conf 1.00 Possible secret in scripts/veyq-server.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/veyq-server.sh:232
high Security checks quality Practices conf 0.84 3 occurrences Foundry mined bad chains: raddatzk/veyq
Comment chain pattern product: bad_chains Repo: raddatzk/veyq Thread: raddatzk/veyq#5 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_has_verificati…
3 occurrences
repo-level (3 hits)
high Security checks quality Quality conf 0.76 4 occurrences Foundry mined schema ui api mismatch: raddatzk/veyq
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: contradicted_by_ci_or_failure_signal …
4 occurrences
repo-level (4 hits)
high Security checks quality Testing conf 0.78 19 occurrences Foundry mined test ci gap after feedback: raddatzk/veyq
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: weak_supervision_needs_…
19 occurrences
repo-level (19 hits)
medium Security checks quality Practices conf 0.62 25 occurrences Foundry mined assumption checks: raddatzk/veyq
Comment chain pattern product: assumption_checks Repo: raddatzk/veyq Thread: raddatzk/veyq#9 Outcome: ambiguous_needs_more_evidence Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_has_ve…
25 occurrences
repo-level (25 hits)
medium Security checks quality maintenance conf 0.70 29 occurrences Foundry mined blueprint gap alignment: raddatzk/veyq
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
29 occurrences
repo-level (29 hits)
medium Security checks quality Practices conf 0.70 7 occurrences Foundry mined unresolved feedback: raddatzk/veyq
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: weak…
7 occurrences
repo-level (7 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — collaboration/src/backendClient.js:27
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 — site/main.js:94
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 hardware Security conf 1.00 Dockerfile runs as root: collaboration/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: frontend/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: infra/reset/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 18 occurrences GitHub Action is tag-pinned rather than SHA-pinned
gradle/actions/setup-gradle@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 18 locations
.github/workflows/container.yml:144, 148, 156, 161, 197, 201, 209, 214, +6 more (14 hits)
.github/workflows/codeql.yml:39, 134, 146 (3 hits)
.github/workflows/ci.yml:48
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/container.yml CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/pages.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in frontend/scripts/generate-openapi.mjs:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
frontend/scripts/generate-openapi.mjs:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in frontend/src/features/memories/components/JournalRenderer.vue:348
Found a known-risky pattern (vue_v_html). Review and replace if possible.
frontend/src/features/memories/components/JournalRenderer.vue:348 Vue v html
medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in frontend/src/views/PublicShareView.vue:636
Found a known-risky pattern (vue_v_html). Review and replace if possible.
frontend/src/views/PublicShareView.vue:636 Vue v html
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in docs/api/auth.openapi.yaml:656
Found a known-risky pattern (weak_hash). Review and replace if possible.
docs/api/auth.openapi.yaml:656 Weak hash
low System graph quality Integrity conf 1.00 19 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CI`, `DB_HOST`, `DB_NAME`, `DB_PORT`, `DB_USER`, `DOCKER_SOCKET`, `HEALTH_PORT`, `JOURNAL_DOCUMENT_IDLE_EVICTION_MS` + 11 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: eclipse-temurin:21-jdk-jammy
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:7 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: eclipse-temurin:21-jre-jammy
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:33 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: nginx:1.27-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
frontend/Dockerfile:9 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 3 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.
3 files, 3 locations
Dockerfile:1
collaboration/Dockerfile:1
frontend/Dockerfile:1
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
infra/reset/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: quay.io/quarkus/ubi9-quarkus-mandrel-builder-image:jdk-21
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:20 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: registry.access.redhat.com/ubi9/ubi-minimal:9.5
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:46 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 17 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
5 files, 17 locations
.github/workflows/ci.yml:39, 42, 59, 62, 81, 84 (6 hits)
.github/workflows/pages.yml:29, 32, 37, 43 (4 hits)
.github/workflows/container.yml:47, 141, 194 (3 hits)
.github/workflows/codeql.yml:34, 124 (2 hits)
.github/workflows/ios-testflight.yml:52, 256 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph software Dead code conf 1.00 Possibly dead Python function: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infra/reset/app.py:320
low System graph software Dead code conf 1.00 Possibly dead Python function: do_POST
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infra/reset/app.py:329
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infra/reset/app.py:411
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: frontend/src/api/generated/apis/AuthApi.ts (1315 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/api/generated/apis/MemoriesApi.ts (1729 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/api/generated/apis/MemoryMediaApi.ts (2483 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/api/generated/apis/PublicSharesApi.ts (5433 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/api/generated/apis/TenantsApi.ts (1474 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/api/generated/apis/UsersApi.ts (2293 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/features/memories/components/MemoryDetail.test.ts (1609 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/i18n/messages.ts (2153 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/5b6079e1-14e3-4336-9fcd-4e25ca76d884/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5b6079e1-14e3-4336-9fcd-4e25ca76d884/

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.