snomiao/otoji
snomiao/otojiClick 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.
Code quality scan: 0 findings (A-, 89/100)
## Code-quality scan: `snomiao/otoji` **Score: 89/100 (A-)** · 0 findings · scanned 2026-06-16 04:38 UTC · 0 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 0 | | MEDIUM | 0 | | LOW | 0 | 📊 [Full filterable report](https://repobility.com/scan/3c3763cb-43a6-4ce1-b2cf-d7db1e268465/) ·  --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/3c3763cb-43a6-4ce1-b2cf-d7db1e268465/_
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.