adam9899/MC-Eternal-2
adam9899/MC-Eternal-2Click 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.
Missing .gitignore
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `adam9899/MC-Eternal-2` **Score: 63/100 (D+)** · 9 findings · scanned 2026-06-05 16:52 UTC · 4,923 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 4 | | MEDIUM | 2 | | LOW | 1 | 📊 [Full filterable report](https://repobility.com/scan/430177c8-6f7f-4f1d-9f21-112878602e42/) ·  ### Top findings 1. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `overrides/kubejs/client_scripts/ponder/tconstruct.js:10` 2. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `overrides/kubejs/client_scripts/ponder/mekanism.js:16` 3. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `overrides/kubejs/client_scripts/ponder/brazier.js:4` 4. **HIGH** `CORE_NO_TESTS` — No test files found 5. **MEDIUM** `CFG006` — Missing .gitignore --- **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/430177c8-6f7f-4f1d-9f21-112878602e42/_
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.