paperlesspaper/epdoptimize
paperlesspaper/epdoptimizeClick 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.
JS: child_process.exec with non-literal
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `paperlesspaper/epdoptimize` **Score: 94/100 (B-)** · 27 findings · scanned 2026-06-05 14:49 UTC · 11,868 LOC | Severity | Count | |---|---| | CRITICAL | 1 | | HIGH | 13 | | MEDIUM | 4 | | LOW | 5 | 📊 [Full filterable report](https://repobility.com/scan/bda76de8-7fc8-46f7-b229-da4ec0e6847d/) ·  ### Top findings 1. **CRITICAL** `SEC010` — Cloud Provider Token `src/dither/wasm-error-diffusion-rgb.ts:23` · A07:2021 Identification & Authentication Failures 2. **HIGH** `MINED099` — Hardcoded Secret `src/dither/wasm-error-diffusion-rgb.ts:23` · ✓ Repobility 3. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `scripts/render-palette-order-comparison.mjs:177` · A10:2021 SSRF 4. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `scripts/dither-with-utils-only.mjs:133` · A10:2021 SSRF 5. **HIGH** `SEC085` — JS: child_process.exec with non-literal `src/dither/functions/color-helpers.ts:7` --- **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/bda76de8-7fc8-46f7-b229-da4ec0e6847d/_
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.