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

yotachy/vdiportal

https://github.com/yotachy/vdiportal · scanned 2026-06-16 01:07 UTC (2 months, 1 week ago)

32 raw signals (0 security + 32 graph)

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

Complete repo analysis

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

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

Showing 29 of 32 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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
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.
CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: vdi-log/CLAUDE.md
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.
vdi-log/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, 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 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 approval-detail.html:338
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
approval-detail.html:338 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in approval.html:196
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
approval.html:196 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in change.html:281
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
change.html:281 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in common.js:75
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
common.js:75 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in faq.html:176
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
faq.html:176 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in incident-new.html:278
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
incident-new.html:278 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in incident.html:308
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
incident.html:308 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in login.html:357
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
login.html:357 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in notice-detail.html:169
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
notice-detail.html:169 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in notice.html:147
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
notice.html:147 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in portal.html:485
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
portal.html:485 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in qna.html:214
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
qna.html:214 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in vdi-log/log.html:998
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
vdi-log/log.html:998 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in vdi_decision_log_IT기획.html:584
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
vdi_decision_log_IT기획.html:584 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in vdi-log/log.html:1784
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
vdi-log/log.html:1784 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in vdi_decision_log_IT기획.html:1154
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
vdi_decision_log_IT기획.html:1154 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in CLAUDE.md:252
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
CLAUDE.md:252 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in login.html:343
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
login.html:343 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in vdi-log/CLAUDE.md:103
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
vdi-log/CLAUDE.md:103 Local storage auth token
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
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 1 source file(s) (ratio 0.00). 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: ci, operator-readme. 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 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/8cf4219f-c557-42a6-8299-7014540228c1/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8cf4219f-c557-42a6-8299-7014540228c1/

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.