7LayerLabs/NBAFO
7LayerLabs/NBAFOClick 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.
localStorage write failures are swallowed silently
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `7LayerLabs/NBAFO` **Score: 84/100 (A-)** · 21 findings · scanned 2026-06-16 02:50 UTC · 25,238 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 1 | | MEDIUM | 10 | | LOW | 7 | 📊 [Full filterable report](https://repobility.com/scan/382d8d72-ae03-46ab-8583-23d8c77e78d8/) ·  ### Top findings 1. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `js/depthchart_ui.js:37` 2. **MEDIUM** `ERR002` — Empty Catch Block: Empty catch blocks hide errors. `js/depthchart_ui.js:90` 3. **MEDIUM** `ERR002` — Empty Catch Block: Empty catch blocks hide errors. `js/airoster_ui.js:19` 4. **MEDIUM** `ERR002` — Empty Catch Block: Empty catch blocks hide errors. `js/aigm.js:91` 5. **MEDIUM** `AGT007` — localStorage write failures are swallowed silently `js/ui.js:592` --- **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/382d8d72-ae03-46ab-8583-23d8c77e78d8/_
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.