m-demare/attempt.nvim
m-demare/attempt.nvimClick 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.
Async function without await — fire-and-forget Promise (AI mistake)
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `m-demare/attempt.nvim` **Score: 79/100 (B)** · 4 findings · scanned 2026-06-05 20:02 UTC · 0 LOC | Severity | Count | |---|---| | CRITICAL | 1 | | HIGH | 3 | | MEDIUM | 0 | | LOW | 0 | 📊 [Full filterable report](https://repobility.com/scan/41212f94-911b-4e7c-906f-c47c75a2c68c/) ·  ### Top findings 1. **CRITICAL** `SEC084` — JS: require() with non-literal `lua/attempt.lua:13` 2. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `lua/attempt/manager.lua:93` 3. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `lua/attempt/interface.lua:128` 4. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `lua/attempt/filedata.lua:83` --- **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/41212f94-911b-4e7c-906f-c47c75a2c68c/_
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.