qingchencloud/clawpanel
qingchencloud/clawpanelClick 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.
Secret-like setting is echoed into a password input value
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `qingchencloud/clawpanel` **Score: 64/100 (C-)** · 59 findings · scanned 2026-05-15 17:15 UTC · 88,826 LOC | Severity | Count | |---|---| | CRITICAL | 1 | | HIGH | 7 | | MEDIUM | 32 | | LOW | 6 | 📊 [Full filterable report](https://repobility.com/scan/efdecec6-e2ef-4fec-829e-1a8beb5bdd4d/) ·  ### Top findings 1. **CRITICAL** `JRN001` — Token handoff appears to use a callback URL or fragment `src/lib/ws-client.js:159` 2. **HIGH** `DKR001` — Docker final stage runs as root `Dockerfile:84` 3. **HIGH** `SEC020` — Secret Printed to Logs `src/main.js:649` · A07:2021 Identification & Authentication Failures 4. **HIGH** `DKC002` — Compose service uses host networking `docker-compose.yml:14` 5. **HIGH** `JRN009` — Secret-like setting is echoed into a password input value `src/pages/gateway.js:168` --- **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/efdecec6-e2ef-4fec-829e-1a8beb5bdd4d/_
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.