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

SDkotarom/v2-veltra-cvr

https://github.com/SDkotarom/v2-veltra-cvr · scanned 2026-06-16 00:05 UTC (2 months, 3 weeks ago)

31 raw signals (0 security + 31 graph)

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

Complete repo analysis

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

JSON
Combined
72.1
/100
Security checks
72
0 findings
System graph
72
88.9% cov · 31 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 0 Medium 23 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 31 Crowd 0 Layer: Frontend 1 Security 16 Cicd 1 Quality 13
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 72.1/100 with 88.9% coverage. It contains 379 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 31 findings — concentrated in security (16), quality (13), frontend (1). Risk profile is low: 0 critical, 0 high, 23 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 28 of 31 actionable findings. 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 — nav.js:565
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 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 license, ci, tests, operator-readme. 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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
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 'direct_innerhtml_assignment' in bottleneck.html:21
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
bottleneck.html:21 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in bottleneck.js:7
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
bottleneck.js:7 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in entry-journey.html:2045
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
entry-journey.html:2045 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in index.html:549
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
index.html:549 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in kpi.html:541
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
kpi.html:541 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in login.html:178
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
login.html:178 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in nav.js:493
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
nav.js:493 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in planning/back-nav.js:10
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
planning/back-nav.js:10 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in planning/index.html:82
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
planning/index.html:82 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in planning/sports-mock/baseball/index.html:679
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
planning/sports-mock/baseball/index.html:679 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in reports/index.html:69
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
reports/index.html:69 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in spot/2026-surface-wireframes.html:735
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
spot/2026-surface-wireframes.html:735 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in summary-detail.js:49
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
summary-detail.js:49 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in funnel-def.js:29
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
funnel-def.js:29 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in auth.js:12
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
auth.js:12 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in login.html:136
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
login.html:136 Local storage auth token
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/generate-week.py:900
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 13 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Maintenance conf 1.00 52 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 127 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 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 Docs conf 1.00 README lacks setup or run instructions
A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.
ReadmeRepo 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
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/09a18e1a-e460-4168-878e-ff3df71c7093/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/09a18e1a-e460-4168-878e-ff3df71c7093/

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.