← Back to scan
File as GitHub Issue repo: helmiwirata111-build/EventHub

Push this scan report to helmiwirata111-build/EventHub

Click 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.

Embedded score card image

This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.

Repobility score card

Issue title

Low visible authorization coverage in route inventory

Curate findings to include

Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.

Top 5 (default)
Severity Rule Title File:line
HIGH CORE_NO_TESTS No test files found —
MED AUC001 [AUC001] No Repobility access matrix policy found: The repository uses web/API frameworks… —
MED WEB003 Public web service has no security.txt .well-known/security.txt
MED JRN003 Frontend API reference is not matched by discovered backend routes app/page.tsx:766
MED AUC002 [AUC002] Low visible authorization coverage in route inventory: Only 0.0% of discovered r… —
MED WEB015 Public web app has no Content Security Policy index.html
MED AUC009 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears … app/api/gemini/chat/route.ts:4
MED CORE_NO_CI No CI/CD configuration found —
LOW AUC005 [AUC005] No authorization-focused tests detected: No test files with common authorization… —
LOW WEB001 Public web app has no robots.txt robots.txt
LOW WEB002 Public web app has no sitemap sitemap.xml
LOW WEB008 Public docs site has no llms.txt llms.txt
LOW WEB011 Public web app has no humans.txt humans.txt
LOW CORE_NO_LICENSE No LICENSE file —
INFO MINED052 [MINED052] Ts Any Typed: : any used as type annotation. Defeats TypeScript type safety. app/api/gemini/chat/route.ts:90
INFO MINED044 [MINED044] Js Console Log Prod: console.log left in code. Should be replaced with logger … app/api/gemini/chat/route.ts:91
Reset to top 5 16 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `helmiwirata111-build/EventHub`

**Score: 83/100 (C)**  ·  16 findings  ·  scanned 2026-05-26 07:12 UTC  ·  2,477 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 1 |
| MEDIUM | 7 |
| LOW | 6 |

📊 [Full filterable report](https://repobility.com/scan/59e4b5bc-7dcc-48d5-899d-7d07ae16ff82/)  ·  ![scorecard](https://repobility.com/scan/59e4b5bc-7dcc-48d5-899d-7d07ae16ff82/report.png?v=1779779524-s2)

### Top findings

1. **HIGH** `CORE_NO_TESTS` — No test files found
2. **MEDIUM** `AUC001` — No Repobility access matrix policy found
   CWE-285 · WSTG-AUTHZ
3. **MEDIUM** `WEB003` — Public web service has no security.txt
   `.well-known/security.txt`
4. **MEDIUM** `JRN003` — Frontend API reference is not matched by discovered backend routes
   `app/page.tsx:766`
5. **MEDIUM** `AUC002` — Low visible authorization coverage in route inventory
   CWE-285 · WSTG-AUTHZ

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/59e4b5bc-7dcc-48d5-899d-7d07ae16ff82/_
Premium account
This scan was submitted by a Enterprise-tier account. Premium accounts have full outreach control â Repobility doesn't pre-fill the 'file as GitHub issue' button for paid users. You can still file the issue manually using the markdown body above (Copy markdown), or contact us if you'd like batch-filing enabled for your account.
Megaproject â high spam risk
Could not determine 'helmiwirata111-build/EventHub' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
I read the warnings â override Cancel

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.