rust-unofficial/awesome-rust
rust-unofficial/awesome-rustClick 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/cache/restore` 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: `rust-unofficial/awesome-rust` **Score: 81/100 (B)** · 24 findings · scanned 2026-06-05 09:56 UTC · 976 LOC | Severity | Count | |---|---| | CRITICAL | 2 | | HIGH | 21 | | MEDIUM | 1 | | LOW | 0 | 📊 [Full filterable report](https://repobility.com/scan/46436537-b4aa-4a4b-8259-f45c4fc1c859/) ·  ### Top findings 1. **CRITICAL** `MINED116` — Workflow uses `secrets.TOKEN_FOR_GITHUB` on a `pull_request` trigger `.github/workflows/rust.yml:41` · ✓ Repobility 2. **CRITICAL** `MINED116` — Workflow uses `secrets.USERNAME_FOR_GITHUB` on a `pull_request` trigger `.github/workflows/rust.yml:40` · ✓ Repobility 3. **HIGH** `MINED115` — Action `mheap/automatic-approve-action` pinned to mutable ref `@v1.1.0` `.github/workflows/approve.yml:12` · ✓ Repobility 4. **HIGH** `MINED115` — Action `actions/cache/save` pinned to mutable ref `@v5` `.github/workflows/rust.yml:44` · ✓ Repobility 5. **HIGH** `MINED115` — Action `actions/cache/restore` pinned to mutable ref `@v5` `.github/workflows/rust.yml:24` · ✓ Repobility --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/46436537-b4aa-4a4b-8259-f45c4fc1c859/_
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.