← Back to scan
File as GitHub Issue repo: leonardomso/33-js-concepts

Push this scan report to leonardomso/33-js-concepts

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

npm package `jsdom` is 2 major version(s) behind (27.4.0 -> 29.1.1)

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… docs/schema-inject.js:55
HIGH MINED115 Action `actions/setup-node` pinned to mutable ref `@v6` .github/workflows/tests.yml:18
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v6` .github/workflows/tests.yml:15
MED SEC136 [SEC136] AI-typical over-broad exception handler swallowing all errors: Catch-all excepti… docs/schema-inject.js:239
MED DEPCUR-NPM npm package `jsdom` is 2 major version(s) behind (27.4.0 -> 29.1.1) package.json
MED GHSA-58qx-3vcg-4xpx ws: GHSA-58qx-3vcg-4xpx package-lock.json
MED CORE_LARGE_FILES Average file size is 680 lines (recommend <300) —
Reset to top 5 7 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `leonardomso/33-js-concepts`

**Score: 77/100 (B+)**  ·  7 findings  ·  scanned 2026-06-05 08:55 UTC  ·  46,889 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 3 |
| MEDIUM | 4 |
| LOW | 0 |

📊 [Full filterable report](https://repobility.com/scan/4bfa7525-6af1-40ce-8d6a-484d6ec05b9b/)  ·  ![scorecard](https://repobility.com/scan/4bfa7525-6af1-40ce-8d6a-484d6ec05b9b/report.png?v=1780649750-s2)

### Top findings

1. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `docs/schema-inject.js:55` · A10:2021 SSRF
2. **HIGH** `MINED115` — Action `actions/setup-node` pinned to mutable ref `@v6`
   `.github/workflows/tests.yml:18` · ✓ Repobility
3. **HIGH** `MINED115` — Action `actions/checkout` pinned to mutable ref `@v6`
   `.github/workflows/tests.yml:15` · ✓ Repobility
4. **MEDIUM** `SEC136` — AI-typical over-broad exception handler swallowing all errors
   `docs/schema-inject.js:239` · CWE-396
5. **MEDIUM** `DEPCUR-NPM` — npm package `jsdom` is 2 major version(s) behind (27.4.0 -> 29.1.1)
   `package.json`

---

**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/4bfa7525-6af1-40ce-8d6a-484d6ec05b9b/_
Megaproject â high spam risk
Could not determine 'leonardomso/33-js-concepts' 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
5/8 findings (62%) 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.