boku7/Loki
boku7/LokiClick 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.
No CI/CD configuration found
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `boku7/Loki` **Score: 84/100 (C+)** · 17 findings · scanned 2026-06-05 01:32 UTC · 10,157 LOC | Severity | Count | |---|---| | CRITICAL | 2 | | HIGH | 1 | | MEDIUM | 2 | | LOW | 8 | 📊 [Full filterable report](https://repobility.com/scan/bf7c966f-70bf-4cf3-a3c2-efbee0268295/) ·  ### Top findings 1. **CRITICAL** `SEC084` — JS: require() with non-literal `agent/renderer.js:48` 2. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive `README.md:136` 3. **HIGH** `SEC040` — innerHTML XSS — template literal with server-supplied data `client/task-queue.js:168` · CWE-79 · A03:2021 Injection (XSS) 4. **MEDIUM** `DEPCUR-NPM` — npm package `node-addon-api` is 1 major version(s) behind (^7.1.1 -> 8.8.0) `dev/COFFLoader/package.json` 5. **MEDIUM** `CORE_NO_CI` — No CI/CD configuration 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/bf7c966f-70bf-4cf3-a3c2-efbee0268295/_
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.