liquid-dre/lighthouse-printing
liquid-dre/lighthouse-printingClick 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.
Public web service has no security.txt
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `liquid-dre/lighthouse-printing` **Score: 64/100 (D+)** · 18 findings · scanned 2026-06-26 20:50 UTC · 3,164 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 2 | | MEDIUM | 5 | | LOW | 7 | 📊 [Full filterable report](https://repobility.com/scan/7d7b084a-8bf2-4244-a8d4-50129cd177d9/) ·  ### Top findings 1. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `app/layout.tsx:35` · A10:2021 SSRF 2. **HIGH** `CORE_NO_TESTS` — No test files found 3. **MEDIUM** `AUC001` — No Repobility access matrix policy found CWE-285 · WSTG-AUTHZ 4. **MEDIUM** `GHSA-qx2v-qp2m-jg93` — postcss: GHSA-qx2v-qp2m-jg93 `package-lock.json` 5. **MEDIUM** `WEB003` — Public web service has no security.txt `.well-known/security.txt` --- **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/7d7b084a-8bf2-4244-a8d4-50129cd177d9/_
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.