harehare/mq
harehare/mqClick 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.
Duplicated implementation block across source files
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `harehare/mq` **Score: 73/100 (C+)** · 17 findings · scanned 2026-05-15 12:20 UTC · 107,180 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 1 | | MEDIUM | 12 | | LOW | 3 | 📊 [Full filterable report](https://repobility.com/scan/e6bb1e32-6148-4bc6-a416-5fb6543fa7c6/) ·  ### Top findings 1. **HIGH** `SEC013` — Path Traversal — User Input in File Path `crates/mq-lsp/src/server.rs:52` · A01:2021 Broken Access Control (path traversal) 2. **MEDIUM** `AUC001` — No Repobility access matrix policy found CWE-285 · WSTG-AUTHZ 3. **MEDIUM** `DKR017` — Dockerfile installs dependencies after copying the full source tree `Dockerfile:7` 4. **MEDIUM** `AIC003` — Duplicated implementation block across source files `crates/mq-wasm/src/script.rs:471` 5. **MEDIUM** `AIC003` — Duplicated implementation block across source files `crates/mq-run/src/debugger.rs:320` --- **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/e6bb1e32-6148-4bc6-a416-5fb6543fa7c6/_
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.