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 2.27s · analysis 3.09s · 3.6 MB · GitHub preflight 536ms

sakisakiel711-ai/remix-of-get-this-app-88

https://github.com/sakisakiel711-ai/remix-of-get-this-app-88.git · scanned 2026-05-26 22:10 UTC (1 week, 2 days ago) · 10 languages

270 findings (54 legacy + 216 scanner) 0th percentile · Typescript · medium (20-100K LoC) Scanner says 73 (lower by 28)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 2 days ago · v2 · 162 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 66.7 0.25 16.68
testing_score 0.0 0.20 0.00
documentation_score 1.0 0.15 0.15
practices_score 40.0 0.15 6.00
code_quality 71.7 0.10 7.17
Overall 1.00 45.0
Severity distribution — click a segment to filter
Active filters: layer: security × excluding tests × Reset all
Scan summary Repository scanned at 72.7/100 with 88.9% coverage. It contains 988 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 108 findings — concentrated in software (43), frontend (38), quality (14). Risk profile is high: 5 critical, 1 high, 18 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 8 of 162 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical Legacy security security .env file committed to repository
Remove .env from version control: git rm --cached .env. Add '.env' to .gitignore. Rotate all exposed credentials.
.env securitylegacy
critical Legacy security credential_exposure conf 1.00 [SEC009] .env File Committed: .env file with secrets committed to repository.
Add .env to .gitignore. Rotate all exposed credentials.
.env credential_exposurelegacy
high Legacy security auth conf 0.83 Secret-like setting is echoed into a password input value
Settings screens sometimes render API keys, tokens, or passwords back into HTML/JSX password fields. That still exposes the secret to page source, browser extensions, screenshots, and DOM scraping.
src/routes/admin.cinetpay.tsx:91 authlegacy
high 9-layer security secrets conf 1.00 .env file present in repo: .env
A raw .env file is in the working tree. Verify it isn't committed and that secrets are in a vault.
secretsconfig
medium 9-layer security owasp conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/ui/chart.tsx:73
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/ui/chart.tsx:73 owaspdangerous_innerhtml
medium 9-layer security owasp conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/routes/__root.tsx:154
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/routes/__root.tsx:154 owaspdangerous_innerhtml
medium 9-layer security owasp conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/routes/faq.tsx:126
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/routes/faq.tsx:126 owaspdangerous_innerhtml
medium 9-layer security owasp conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/routes/pages.$slug.tsx:155
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/routes/pages.$slug.tsx:155 owaspdangerous_innerhtml
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/fd1aee94-3037-47ed-8281-ef5821ab1d26/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fd1aee94-3037-47ed-8281-ef5821ab1d26/

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.