airlift/airlift
airlift/airliftClick 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.
Server-Side Request Forgery (SSRF) — outbound HTTP from user input
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `airlift/airlift` **Score: 71/100 (B-)** · 46 findings · scanned 2026-06-06 01:11 UTC · 113,718 LOC | Severity | Count | |---|---| | CRITICAL | 1 | | HIGH | 17 | | MEDIUM | 0 | | LOW | 17 | 📊 [Full filterable report](https://repobility.com/scan/de2414e5-24ff-4da0-bad1-f1bce218faa1/) ·  ### Top findings 1. **CRITICAL** `MINED019` — Ssti Jinja From String `mcp/src/main/java/io/airlift/mcp/handler/ResourceTemplateHandler.java:13` · CWE-94 · ✓ Repobility 2. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `stats/src/main/java/io/airlift/stats/MeterStat.java:35` 3. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `security/src/main/java/io/airlift/security/cert/CertificateBuilder.java:250` 4. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `http-client/src/main/java/io/airlift/http/client/RequestStats.java:60` 5. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `api/src/main/java/io/airlift/api/openapi/models/Server.java:18` · 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/de2414e5-24ff-4da0-bad1-f1bce218faa1/_
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.