lrrok/are-you-ok
lrrok/are-you-okClick 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.
Empty Catch Block: Empty catch blocks hide errors.
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `lrrok/are-you-ok` **Score: 73/100 (D)** · 12 findings · scanned 2026-05-26 22:41 UTC · 223 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 3 | | MEDIUM | 5 | | LOW | 4 | 📊 [Full filterable report](https://repobility.com/scan/0cbd5404-c9ad-4b41-94f4-59a5cb0e9c40/) ·  ### Top findings 1. **HIGH** `MINED027` — React State Array Mutation `app.js:163` · CWE-682 · ✓ Repobility 2. **HIGH** `SEC040` — innerHTML XSS — template literal with server-supplied data `app.js:67` · CWE-79 · A03:2021 Injection (XSS) 3. **HIGH** `CORE_NO_TESTS` — No test files found 4. **MEDIUM** `CFG006` — Missing .gitignore 5. **MEDIUM** `ERR002` — Empty Catch Block: Empty catch blocks hide errors. `app.js:215` --- **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/0cbd5404-c9ad-4b41-94f4-59a5cb0e9c40/_
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.