maruturisaisasidhar/TEXT-TOOLS
maruturisaisasidhar/TEXT-TOOLSClick the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.
This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.
Express POST /api/process-text has no auth
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `maruturisaisasidhar/TEXT-TOOLS` **Score: 74/100 (C-)** · 22 findings · scanned 2026-05-22 12:48 UTC · 1,156 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 11 | | MEDIUM | 4 | | LOW | 2 | 📊 [Full filterable report](https://repobility.com/scan/d989086a-79cf-4b87-b2b1-b98172f7be9b/) ·  ### Top findings 1. **HIGH** `SEC040` — innerHTML XSS — template literal with server-supplied data `frontend/chrome-extension/content.js:18` · CWE-79 · A03:2021 Injection (XSS) 2. **HIGH** `SEC135` — Auth/permission check missing on AI-generated endpoint `backend/server.js:28` · CWE-862 3. **HIGH** `SEC135` — Auth/permission check missing on AI-generated endpoint `backend/chrome-proxy/server.js:27` · CWE-862 4. **HIGH** `SEC100` — CORS permissive Access-Control-Allow-Origin: * `backend/chrome-proxy/server.js:18` · A05:2021 Security Misconfiguration 5. **HIGH** `MINED113` — Express POST /api/process-text has no auth `backend/chrome-proxy/server.js:57` · ✓ Repobility --- **Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately. --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/d989086a-79cf-4b87-b2b1-b98172f7be9b/_
The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.
For real security findings on big repos: use the project's SECURITY.md or
private advisory flow instead of a public issue.