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.

Scan timing: clone 1.63s · analysis 1.2s · 0.8 MB · GitHub preflight 459ms

maruturisaisasidhar/vcodex

https://github.com/maruturisaisasidhar/vcodex.git · scanned 2026-05-22 12:47 UTC (2 weeks ago) · 10 languages

172 findings (44 legacy + 128 scanner) 26th percentile · Javascript · small (2-20K LoC) Scanner says 63 (lower by 15)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks ago · v2 · 108 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 100.0 0.15 15.00
security_score 49.4 0.25 12.35
testing_score 0.0 0.20 0.00
documentation_score 40.7 0.15 6.11
practices_score 42.0 0.15 6.30
code_quality 80.0 0.10 8.00
Overall 1.00 47.8
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in src/firebase/config.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in src/firebase/config.js:13; move to env var / secrets manager.
src/firebase/config.js:13
#2
.env file present in repo: .env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#3
`dangerouslySetInnerHTML` used in a React component — src/components/exam/student/QuestionViewer.jsx:22
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#4
Dangling fetch: POST https://generativelanguage.googleapis.com/v1beta/models/gemini-2.0-flash:generateContent?key=${API_KEY} (server.js:30)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#5
Dangling fetch: POST https://generativelanguage.googleapis.com/v1beta/models/gemini-2.0-flash-exp:generateContent?key=${API_KEY} (server-production.js:55)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#6
Insecure pattern 'dangerous_innerhtml' in src/components/exam/student/QuestionViewer.jsx:22
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
src/components/exam/student/QuestionViewer.jsx:22
#7
No CI/CD pipelines detected
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
#8
Very low test-to-source ratio
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity
#9
`fetch()` without try/.catch or AbortSignal — server-production.js:55
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in server-production.js:55, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#10
Frontend route `/faculty-setup` has no Link/navigate to it — src/App.jsx
GapSeverity.MEDIUM Layer.QUALITY score 0.214
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/App.jsx, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/8aacf6ca-6284-49d9-b68d-7c6c5b949e6f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8aacf6ca-6284-49d9-b68d-7c6c5b949e6f/

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.