EbookFoundation/free-programming-books
EbookFoundation/free-programming-booksClick 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.
Action `actions/checkout` pinned to mutable ref `@v5`
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `EbookFoundation/free-programming-books` **Score: 82/100 (B)** · 22 findings · scanned 2026-06-05 04:09 UTC · 605 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 19 | | MEDIUM | 3 | | LOW | 0 | 📊 [Full filterable report](https://repobility.com/scan/6e12f592-776f-45a0-bace-d304b3f7903a/) ·  ### Top findings 1. **HIGH** `MINED115` — Action `eps1lon/actions-label-merge-conflict` pinned to mutable ref `@v3.1.0` `.github/workflows/detect-conflicting-prs.yml:32` · ✓ Repobility 2. **HIGH** `MINED115` — Action `actions/upload-artifact` pinned to mutable ref `@v7` `.github/workflows/rtl-ltr-linter.yml:97` · ✓ Repobility 3. **HIGH** `MINED115` — Action `tj-actions/changed-files` pinned to mutable ref `@v46` `.github/workflows/rtl-ltr-linter.yml:43` · ✓ Repobility 4. **HIGH** `MINED115` — Action `actions/setup-python` pinned to mutable ref `@v6` `.github/workflows/rtl-ltr-linter.yml:23` · ✓ Repobility 5. **HIGH** `MINED115` — Action `actions/checkout` pinned to mutable ref `@v5` `.github/workflows/rtl-ltr-linter.yml:15` · ✓ Repobility --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/6e12f592-776f-45a0-bace-d304b3f7903a/_
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.