← Back to scan
File as GitHub Issue repo: aeshell/aesh

Push this scan report to aeshell/aesh

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

Binary file `examples/dev/tamboui/toolkit/app/ToolkitRunner.class` committed in source rep

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… aesh/src/main/java/org/aesh/command/imp…:127
HIGH SEC029 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTT… aesh/src/main/java/org/aesh/command/imp…:36
HIGH MINED134 Binary file `examples/org/aesh/readline/tty/terminal/TerminalConnection.class` committed … examples/org/aesh/readline/tty/terminal…:1
HIGH MINED134 Binary file `examples/dev/tamboui/backend/aesh/AeshBackend.class` committed in source repo examples/dev/tamboui/backend/aesh/AeshB…:1
HIGH MINED134 Binary file `examples/dev/tamboui/toolkit/app/ToolkitRunner.class` committed in source re… examples/dev/tamboui/toolkit/app/Toolki…:1
HIGH MINED134 Binary file `examples/dev/tamboui/tui/TerminalInputReader.class` committed in source repo examples/dev/tamboui/tui/TerminalInputR…:1
HIGH MINED134 Binary file `examples/dev/tamboui/tui/TuiRunner.class` committed in source repo examples/dev/tamboui/tui/TuiRunner.class:1
HIGH MINED134 Binary file `examples/dev/tamboui/terminal/AbstractBackend.class` committed in source repo examples/dev/tamboui/terminal/AbstractB…:1
HIGH MINED134 Binary file `examples/dev/tamboui/terminal/Backend.class` committed in source repo examples/dev/tamboui/terminal/Backend.c…:1
HIGH MINED115 Action `actions/setup-java` pinned to mutable ref `@v5` .github/workflows/release.yml:25
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v6` .github/workflows/release.yml:20
HIGH MINED115 Action `actions/setup-java` pinned to mutable ref `@v5` .github/workflows/main.yml:12
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v6` .github/workflows/main.yml:10
MED SEC031 [SEC031] Catastrophic Backtracking Regex (ReDoS): Regex contains nested quantifiers like … aesh/src/main/java/org/aesh/util/Proper…:9
LOW SEC132 [SEC132] String concat where the language has interpolation (AI style drift): String buil… aesh/src/main/java/org/aesh/command/opt…:51
LOW SEC132 [SEC132] String concat where the language has interpolation (AI style drift): String buil… aesh/src/main/java/org/aesh/command/imp…:83
LOW SEC132 [SEC132] String concat where the language has interpolation (AI style drift): String buil… aesh/src/main/java/org/aesh/command/exp…:88
LOW AIC003 Duplicated implementation block across source files aesh/src/main/java/org/aesh/command/ali…:31
LOW AIC003 Duplicated implementation block across source files aesh-tamboui/src/main/java/org/aesh/tam…:13
Reset to top 5 19 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `aeshell/aesh`

**Score: 81/100 (B+)**  ·  19 findings  ·  scanned 2026-06-05 22:59 UTC  ·  74,211 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 13 |
| MEDIUM | 1 |
| LOW | 5 |

📊 [Full filterable report](https://repobility.com/scan/bf4fcfe6-0b40-4a64-8a17-c610c6d05d3f/)  ·  ![scorecard](https://repobility.com/scan/bf4fcfe6-0b40-4a64-8a17-c610c6d05d3f/report.png?v=1780700379-s2)

### Top findings

1. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `aesh/src/main/java/org/aesh/command/impl/internal/ProcessedCommandBuilder.java:127` · A10:2021 SSRF
2. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `aesh/src/main/java/org/aesh/command/impl/converter/URLConverter.java:36` · A10:2021 SSRF
3. **HIGH** `MINED134` — Binary file `examples/org/aesh/readline/tty/terminal/TerminalConnection.class` committed i
   `examples/org/aesh/readline/tty/terminal/TerminalConnection.class:1` · ✓ Repobility
4. **HIGH** `MINED134` — Binary file `examples/dev/tamboui/backend/aesh/AeshBackend.class` committed in source repo
   `examples/dev/tamboui/backend/aesh/AeshBackend.class:1` · ✓ Repobility
5. **HIGH** `MINED134` — Binary file `examples/dev/tamboui/toolkit/app/ToolkitRunner.class` committed in source rep
   `examples/dev/tamboui/toolkit/app/ToolkitRunner.class:1` · ✓ Repobility

---

**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/bf4fcfe6-0b40-4a64-8a17-c610c6d05d3f/_
Megaproject â high spam risk
Could not determine 'aeshell/aesh' 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.
Already filed
11/21 findings (52%) on this scan are already flagged as test-file, won't-fix, or suppressed. The scan is too noisy to file as a single issue. Curate down to specific actionable findings, or address the FP source first.
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.