← Back to scan
File as GitHub Issue repo: rcarmo/piclaw

Push this scan report to rcarmo/piclaw

Click 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.

Embedded score card image

This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.

Repobility score card

Issue title

Server-Side Request Forgery (SSRF) — outbound HTTP from user input

Curate findings to include

Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.

Top 5 (default)
Severity Rule Title File:line
HIGH SEC006 [SEC006] XSS Risk: Direct HTML injection without sanitization. runtime/src/channels/web/http/pdf-viewe…:142
HIGH SEC006 [SEC006] XSS Risk: Direct HTML injection without sanitization. runtime/src/channels/web/http/html-view…:61
HIGH SEC029 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTT… runtime/scripts/azure-openai-proxy.ts:32
HIGH SEC029 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTT… runtime/scripts/azure-openai-harness.ts:317
HIGH SEC029 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTT… runtime/desktop/electrobun-main.ts:121
MED CFG006 [CFG006] Missing .gitignore: No .gitignore file. Risk of committing secrets and build art… —
MED SEC015 [SEC015] Insecure Randomness for Security: Weak PRNG used in security-sensitive context. … runtime/extensions/experimental/m365/sh…:1742
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. runtime/desktop/electrobun-main.ts:56
Reset to top 5 8 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `rcarmo/piclaw`

**Score: 70/100 (C+)**  ·  19 findings  ·  scanned 2026-05-16 12:50 UTC  ·  85,995 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 5 |
| MEDIUM | 3 |
| LOW | 0 |

📊 [Full filterable report](https://repobility.com/scan/508becbf-b45d-4fe9-b5f3-d49a26a57d6b/)  ·  ![scorecard](https://repobility.com/scan/508becbf-b45d-4fe9-b5f3-d49a26a57d6b/report.png?v=1778935801-s2)

### Top findings

1. **HIGH** `SEC006` — XSS Risk
   `runtime/src/channels/web/http/pdf-viewer-route.ts:142` · A03:2021 Injection
2. **HIGH** `SEC006` — XSS Risk
   `runtime/src/channels/web/http/html-viewer-route.ts:61` · A03:2021 Injection
3. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `runtime/scripts/azure-openai-proxy.ts:32` · A10:2021 SSRF
4. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `runtime/scripts/azure-openai-harness.ts:317` · A10:2021 SSRF
5. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `runtime/desktop/electrobun-main.ts:121` · A10:2021 SSRF

---

**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/508becbf-b45d-4fe9-b5f3-d49a26a57d6b/_
Megaproject â high spam risk
Could not determine 'rcarmo/piclaw' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
Open in GitHub to file this issue Cancel

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.