ohmyzsh/ohmyzsh
ohmyzsh/ohmyzshClick 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.
Detected a Generic API Key, potentially exposing access to various services and sensitive
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `ohmyzsh/ohmyzsh` **Score: 69/100 (B)** · 29 findings · scanned 2026-06-05 04:33 UTC · 1,320 LOC | Severity | Count | |---|---| | CRITICAL | 6 | | HIGH | 8 | | MEDIUM | 4 | | LOW | 5 | 📊 [Full filterable report](https://repobility.com/scan/b387ada8-9962-4839-a2be-d5dbb09d4cdd/) ·  ### Top findings 1. **CRITICAL** `MINED013` — Password In Url `plugins/drush/drush.plugin.zsh:64` · CWE-200 · ✓ Repobility 2. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive `plugins/macos/spotify:57` 3. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive `plugins/dotenv/README.md:29` 4. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive `plugins/dotenv/README.md:21` 5. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive `plugins/dotenv/README.md:20` --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/b387ada8-9962-4839-a2be-d5dbb09d4cdd/_
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.