RCode12/izakaya-tracker
RCode12/izakaya-trackerClick 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.
No Repobility access matrix policy found
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `RCode12/izakaya-tracker` **Score: 87/100 (C)** · 24 findings · scanned 2026-05-27 13:32 UTC · 1,826 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 4 | | MEDIUM | 7 | | LOW | 7 | 📊 [Full filterable report](https://repobility.com/scan/0f2b42eb-10ba-43f8-9c77-1b61bea63439/) ·  ### Top findings 1. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `components/visits/TabelogUrlInput.tsx:53` · A10:2021 SSRF 2. **HIGH** `JRN009` — Secret-like setting is echoed into a password input value `app/(auth)/signup/page.tsx:81` 3. **HIGH** `JRN009` — Secret-like setting is echoed into a password input value `app/(auth)/login/page.tsx:63` 4. **HIGH** `CORE_NO_TESTS` — No test files found 5. **MEDIUM** `AUC001` — No Repobility access matrix policy found CWE-285 · WSTG-AUTHZ --- **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/0f2b42eb-10ba-43f8-9c77-1b61bea63439/_
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.