← Back to scan
File as GitHub Issue repo: infosecstreams/infosecstreams.github.io

Push this scan report to infosecstreams/infosecstreams.github.io

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

GitHub Action `actions/checkout@v3` is 3 major version(s) behind (latest v6.0.3)

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 SEC029 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTT… js/sort.js:147
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v3` .github/workflows/main.yaml:24
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. js/sort.js:238
MED DEPCUR-GHA GitHub Action `actions/checkout@v3` is 3 major version(s) behind (latest v6.0.3) .github/workflows/main.yaml:24
Reset to top 5 4 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `infosecstreams/infosecstreams.github.io`

**Score: 86/100 (B)**  ·  4 findings  ·  scanned 2026-06-05 18:19 UTC  ·  238 LOC

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

📊 [Full filterable report](https://repobility.com/scan/d59ef752-3f00-45ae-a85c-7cf83affbc5c/)  ·  ![scorecard](https://repobility.com/scan/d59ef752-3f00-45ae-a85c-7cf83affbc5c/report.png?v=1780683589-s2)

### Top findings

1. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `js/sort.js:147` · A10:2021 SSRF
2. **HIGH** `MINED115` — Action `actions/checkout` pinned to mutable ref `@v3`
   `.github/workflows/main.yaml:24` · ✓ Repobility
3. **MEDIUM** `ERR002` — Empty Catch Block: Empty catch blocks hide errors.
   `js/sort.js:238`
4. **MEDIUM** `DEPCUR-GHA` — GitHub Action `actions/checkout@v3` is 3 major version(s) behind (latest v6.0.3)
   `.github/workflows/main.yaml:24`

---

**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/d59ef752-3f00-45ae-a85c-7cf83affbc5c/_
Megaproject â high spam risk
Could not determine 'infosecstreams/infosecstreams.github.io' 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
2/5 findings (40%) 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.
I read the warnings â override 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.