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

supergenedev/yovo_

https://github.com/supergenedev/yovo_ · scanned 2026-06-16 00:26 UTC (2 months, 2 weeks ago)

38 raw signals (0 security + 38 graph)

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

Complete repo analysis

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

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

Showing 24 of 29 actionable findings. 38 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 Possible secret in backend/db/seeds/01_users.rb
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
backend/db/seeds/01_users.rb:1
critical System graph security Secrets conf 1.00 Possible secret in backend/db/seeds/06_admin.rb
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
backend/db/seeds/06_admin.rb:2
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: backend/.env.development
`backend/.env.development` 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.
backend/.env.development ConfigEnv fileRuntime env
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: frontend/.env.development
`frontend/.env.development` 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.
frontend/.env.development ConfigEnv fileRuntime env
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: frontend/.env.production
`frontend/.env.production` 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.
frontend/.env.production ConfigEnv fileRuntime env
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/libraries/sg-ds-library/components/Icon.tsx:108
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 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: 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 quality Integrity conf 1.00 5 occurrences Frontend route `/home` has no Link/navigate to it — frontend/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
5 occurrences
repo-level (5 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
ruby/setup-ruby@v1 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 17, 36, 67
backend/.github/workflows/ci.yml:17, 36, 67 (3 hits)
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/libraries/sg-ds-library/components/Icon.tsx:108
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/libraries/sg-ds-library/components/Icon.tsx:108 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/stores/auth.ts:21
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/stores/auth.ts:21 Local storage auth token
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 70 placeholder/mock markers across 22 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
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.
backend/Dockerfile Ports
medium System graph network Security conf 1.00 Privileged port 127 in use
Port 127 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
backend/config/deploy.yml Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
6 test file(s) for 175 source file(s) (ratio 0.03). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: docker.io/library/ruby:$RUBY_VERSION-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:12 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: nginx: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:11 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-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:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 14, 33, 41, 64
backend/.github/workflows/ci.yml:14, 33, 41, 64 (4 hits)
CI/CD securitySupply chainGithub actions
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo 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 api Wiring conf 1.00 Unused endpoint: USE /icons
`frontend/vite.config.ts` declares `USE /icons` 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
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/e0f30c8f-f0cf-4b1a-b54f-0755640b7570/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e0f30c8f-f0cf-4b1a-b54f-0755640b7570/

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.