← Back to scan
File as GitHub Issue repo: EvanBacon/serve-sim

Push this scan report to EvanBacon/serve-sim

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

Empty Catch Block: Empty catch blocks hide errors.

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 SEC029 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTT… packages/serve-sim/Sources/SimStreamHel…:269
HIGH SEC029 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTT… packages/serve-sim-client/src/transport…:160
HIGH SEC029 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTT… packages/serve-sim-client/src/simulator…:198
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. packages/serve-sim/src/client/hooks/use…:44
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. packages/serve-sim/src/client/client.tsx:536
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. packages/serve-sim-client/src/simulator…:311
MED AUC001 [AUC001] No Repobility access matrix policy found: The repository uses web/API frameworks… —
MED AGT007 localStorage write failures are swallowed silently packages/serve-sim/src/client/hooks/use…:100
MED AGT007 localStorage write failures are swallowed silently packages/serve-sim/src/client/hooks/use…:45
Reset to top 5 9 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `EvanBacon/serve-sim`

**Score: 86/100 (B+)**  ·  9 findings  ·  scanned 2026-05-16 22:30 UTC  ·  22,493 LOC

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

📊 [Full filterable report](https://repobility.com/scan/445e6e2e-8b99-4dc2-ab93-4be9669a8976/)  ·  ![scorecard](https://repobility.com/scan/445e6e2e-8b99-4dc2-ab93-4be9669a8976/report.png?v=1778970657-s2)

### Top findings

1. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `packages/serve-sim/Sources/SimStreamHelper/AccessibilityBridge.swift:269` · A10:2021 SSRF
2. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `packages/serve-sim-client/src/transport.ts:160` · A10:2021 SSRF
3. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `packages/serve-sim-client/src/simulator/SimulatorView.tsx:198` · A10:2021 SSRF
4. **MEDIUM** `ERR002` — Empty Catch Block: Empty catch blocks hide errors.
   `packages/serve-sim/src/client/hooks/use-mjpeg-stream.ts:44`
5. **MEDIUM** `ERR002` — Empty Catch Block: Empty catch blocks hide errors.
   `packages/serve-sim/src/client/client.tsx:536`

---

**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/445e6e2e-8b99-4dc2-ab93-4be9669a8976/_
Already filed
Repobility already filed issue #62 on this repo on 2026-05-16. Filing again would be duplicate spam.
View existing issue
Megaproject â high spam risk
Could not determine 'EvanBacon/serve-sim' 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.
I read the warnings â override 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.