Taiwo703/API-project
Taiwo703/API-projectClick 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.
No Repobility access matrix policy found
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `Taiwo703/API-project` **Score: 70/100 (D+)** · 11 findings · scanned 2026-05-28 14:23 UTC · 30 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 2 | | MEDIUM | 6 | | LOW | 2 | 📊 [Full filterable report](https://repobility.com/scan/4c680485-cbd6-4f92-8a13-181a1478b4a9/) ·  ### Top findings 1. **HIGH** `AUC003` — Object-level route lacks visible authorization: A route with an object id-like parameter d `app.js:17` · CWE-639 · API1:2023 Broken Object Level Authorization 2. **HIGH** `CORE_NO_TESTS` — No test files found 3. **MEDIUM** `CFG006` — Missing .gitignore 4. **MEDIUM** `SEC034` — Log Injection / Log Forging — unsanitized user input in log `app.js:18` · CWE-117 · A09:2021 Security Logging & Monitoring Failures 5. **MEDIUM** `AUC001` — No Repobility access matrix policy found CWE-285 · WSTG-AUTHZ --- **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/4c680485-cbd6-4f92-8a13-181a1478b4a9/_
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.