← Back to scan
File as GitHub Issue repo: OpenDocCN/love-course-notes-zh

Push this scan report to OpenDocCN/love-course-notes-zh

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

No test files found

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
CRIT MINED123 [MINED123] Trojan Source bidi character (LRE) in source: Line 1 contains a Unicode bidire… asset/docsify-katex.js:1
HIGH SEC085 [SEC085] JS: child_process.exec with non-literal: child_process.exec with user-derived in… asset/edit.js:9
HIGH DKR014 Dockerfile copies the entire context without .dockerignore Dockerfile:2
HIGH MINED118 [MINED118] Dockerfile FROM `httpd:2.4` not pinned by digest: `FROM httpd:2.4` resolves th… Dockerfile:1
HIGH CORE_NO_TESTS No test files found —
MED CFG006 [CFG006] Missing .gitignore: No .gitignore file. Risk of committing secrets and build art… —
MED SEC045 [SEC045] eval()/exec() on stored or user-supplied data: eval() and exec() on data — even … asset/edit.js:9
MED SEC041 [SEC041] Tabnabbing — target="_blank" without rel="noopener noreferrer": <a target="_blan… asset/edit.js:13
MED SEC041 [SEC041] Tabnabbing — target="_blank" without rel="noopener noreferrer": <a target="_blan… asset/docsify-apachecn-footer.js:8
MED DKR007 Docker build context has no .dockerignore .dockerignore
MED DKR001 Docker final stage has no non-root USER Dockerfile:1
MED CORE_NO_CI No CI/CD configuration found —
INFO MINED043 [MINED043] Http Not Https: Hardcoded http:// (not localhost) for endpoints that handle cr… asset/docsify-apachecn-footer.js:8
Reset to top 5 13 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `OpenDocCN/love-course-notes-zh`

**Score: 70/100 (C)**  ·  13 findings  ·  scanned 2026-06-05 23:54 UTC  ·  432 LOC

| Severity | Count |
|---|---|
| CRITICAL | 1 |
| HIGH | 4 |
| MEDIUM | 7 |
| LOW | 0 |

📊 [Full filterable report](https://repobility.com/scan/3bf4ce8e-00ee-4875-9e58-be41bcb66844/)  ·  ![scorecard](https://repobility.com/scan/3bf4ce8e-00ee-4875-9e58-be41bcb66844/report.png?v=1780703644-s2)

### Top findings

1. **CRITICAL** `MINED123` — Trojan Source bidi character (LRE) in source: Line 1 contains a Unicode bidirectional over
   `asset/docsify-katex.js:1` · ✓ Repobility
2. **HIGH** `SEC085` — JS: child_process.exec with non-literal
   `asset/edit.js:9`
3. **HIGH** `DKR014` — Dockerfile copies the entire context without .dockerignore
   `Dockerfile:2`
4. **HIGH** `MINED118` — Dockerfile FROM `httpd:2.4` not pinned by digest: `FROM httpd:2.4` resolves the tag at bui
   `Dockerfile:1` · ✓ Repobility
5. **HIGH** `CORE_NO_TESTS` — No test files found

---

**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/3bf4ce8e-00ee-4875-9e58-be41bcb66844/_
Megaproject â high spam risk
Could not determine 'OpenDocCN/love-course-notes-zh' 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.
Open in GitHub to file this issue 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.