← Back to scan
File as GitHub Issue repo: AkihikoWatanabe/paper_notes

Push this scan report to AkihikoWatanabe/paper_notes

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

Action `actions/checkout` pinned to mutable ref `@v2`: `uses

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 SEC078 [SEC078] Python: requests without timeout: requests.get/post without a timeout will hang … .github/scripts/correct_issue.py:57
HIGH SEC029 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTT… .github/scripts/correct_issue.py:42
HIGH MINED115 [MINED115] Action `actions/checkout` pinned to mutable ref `@v2`: `uses: actions/checkout… .github/workflows/build_and_deploy.yml:13
HIGH MINED115 [MINED115] Action `actions/setup-python` pinned to mutable ref `@v2`: `uses: actions/setu… .github/workflows/issue_correction.yml:15
HIGH MINED115 [MINED115] Action `actions/checkout` pinned to mutable ref `@v2`: `uses: actions/checkout… .github/workflows/issue_correction.yml:13
HIGH MINED118 [MINED118] Dockerfile FROM `python:3.10-slim-bullseye` not pinned by digest: `FROM python… Dockerfile:1
MED DKR007 Docker build context has no .dockerignore .dockerignore
MED DKR001 Docker final stage has no non-root USER Dockerfile:1
LOW WEB010 sitemap.xml contains non-HTTPS public URLs docs/sitemap.xml
LOW DKR010 Dockerfile leaves apt package indexes in the image layer Dockerfile:2
LOW DKR012 Dockerfile keeps pip download cache Dockerfile:3
LOW DKR011 Dockerfile installs recommended OS packages Dockerfile:2
LOW DKC010 Compose service lacks no-new-privileges hardening docker-compose.yaml
LOW DKC006 Compose service does not declare a runtime user docker-compose.yaml
INFO MINED067 [MINED067] Python Requests No Timeout: requests.get/post/etc. without timeout= can hang f… .github/scripts/correct_issue.py:57
INFO MINED043 [MINED043] Http Not Https: Hardcoded http:// (not localhost) for endpoints that handle cr… .github/scripts/correct_issue.py:51
Reset to top 5 16 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `AkihikoWatanabe/paper_notes`

**Score: 83/100 (B+)**  ·  16 findings  ·  scanned 2026-06-06 00:10 UTC  ·  1,308 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 6 |
| MEDIUM | 2 |
| LOW | 6 |

📊 [Full filterable report](https://repobility.com/scan/6a5c839b-199c-4247-be24-b1491f2e403c/)  ·  ![scorecard](https://repobility.com/scan/6a5c839b-199c-4247-be24-b1491f2e403c/report.png?v=1780704636-s2)

### Top findings

1. **HIGH** `SEC078` — Python: requests without timeout
   `.github/scripts/correct_issue.py:57` · A05:2021 Security Misconfiguration
2. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `.github/scripts/correct_issue.py:42` · A10:2021 SSRF
3. **HIGH** `MINED115` — Action `actions/checkout` pinned to mutable ref `@v2`: `uses
   `.github/workflows/build_and_deploy.yml:13` · ✓ Repobility
4. **HIGH** `MINED115` — Action `actions/setup-python` pinned to mutable ref `@v2`: `uses
   `.github/workflows/issue_correction.yml:15` · ✓ Repobility
5. **HIGH** `MINED115` — Action `actions/checkout` pinned to mutable ref `@v2`: `uses
   `.github/workflows/issue_correction.yml:13` · ✓ 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/6a5c839b-199c-4247-be24-b1491f2e403c/_
Megaproject â high spam risk
Could not determine 'AkihikoWatanabe/paper_notes' 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
8/17 findings (47%) 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.
Open in GitHub to file this issue Filing guard overridden 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.