AIMEHS/ehs-hub
AIMEHS/ehs-hubClick 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.
High cognitive complexity: Function `main` has cognitive complexity 31 (SonarSource scale)
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `AIMEHS/ehs-hub` **Score: 68/100 (B-)** · 23 findings · scanned 2026-06-16 02:51 UTC · 433 LOC | Severity | Count | |---|---| | CRITICAL | 1 | | HIGH | 7 | | MEDIUM | 9 | | LOW | 6 | 📊 [Full filterable report](https://repobility.com/scan/f0d86c64-bad2-4394-807e-0ca89494e7bd/) ·  ### Top findings 1. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive `index.html:544` 2. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `sw.js:18` · A10:2021 SSRF 3. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `scripts/scrape_adi.py:62` 4. **HIGH** `SEC103` — LDAP injection — non-constant search filter `scripts/scrape_adi.py:96` · A03:2021 Injection 5. **HIGH** `COMP001` — High cognitive complexity: Function `main` has cognitive complexity 31 (SonarSource scale) `scripts/scrape_adi.py:106` --- **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/f0d86c64-bad2-4394-807e-0ca89494e7bd/_
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.