mateiszakwork-cloud/hiro
mateiszakwork-cloud/hiroClick 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.
CORS permissive Access-Control-Allow-Origin: *
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `mateiszakwork-cloud/hiro` **Score: 75/100 (C)** · 39 findings · scanned 2026-05-25 15:37 UTC · 17,816 LOC | Severity | Count | |---|---| | CRITICAL | 2 | | HIGH | 9 | | MEDIUM | 5 | | LOW | 10 | 📊 [Full filterable report](https://repobility.com/scan/ecbe478e-97ee-4d3d-90ff-98c1aca2692b/) ·  ### Top findings 1. **CRITICAL** `SEC009` — .env File Committed: .env file with secrets committed to repository. `.env` 2. **CRITICAL** `CORE_ENV_FILE` — .env file committed to repository `.env` 3. **HIGH** `SEC100` — CORS permissive Access-Control-Allow-Origin: * `supabase/functions/draft-tracker-message/index.ts:5` · A05:2021 Security Misconfiguration 4. **HIGH** `SEC100` — CORS permissive Access-Control-Allow-Origin: * `supabase/functions/draft-outreach-messages/index.ts:4` · A05:2021 Security Misconfiguration 5. **HIGH** `SEC100` — CORS permissive Access-Control-Allow-Origin: * `supabase/functions/calculate-match-score/index.ts:5` · A05:2021 Security Misconfiguration --- **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/ecbe478e-97ee-4d3d-90ff-98c1aca2692b/_
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.