unslothai/unsloth
Push this scan report to unslothai/unsloth
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.
Issue title
Path Traversal — User Input in File Path
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.
Issue body (markdown)
## Code-quality scan: `unslothai/unsloth` **Score: 62/100 (B-)** · 57 findings · scanned 2026-05-15 07:28 UTC · 286,768 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 5 | | MEDIUM | 38 | | LOW | 1 | 📊 [Full filterable report](https://repobility.com/scan/098a2aee-fee1-458b-bcaa-d4f661adc5a3/) ·  ### Top findings 1. **HIGH** `SEC016` — LLM Prompt Injection — User Input in AI Prompt `unsloth/chat_templates.py:1793` 2. **HIGH** `SEC020` — Secret Printed to Logs `unsloth/chat_templates.py:1921` · A07:2021 Identification & Authentication Failures 3. **HIGH** `SEC005` — Command Injection Risk `unsloth/tokenizer_utils.py:1692` · A03:2021 Injection 4. **HIGH** `SEC005` — Command Injection Risk `unsloth/_gpu_init.py:294` · A03:2021 Injection 5. **HIGH** `SEC013` — Path Traversal — User Input in File Path `studio/install_llama_prebuilt.py:853` · A01:2021 Broken Access Control (path traversal) --- **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/098a2aee-fee1-458b-bcaa-d4f661adc5a3/_
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.