Taiwo703/API-project

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

Scan timing: clone 3.14s · analysis 0.19s · GitHub API rate-limit (preflight)

https://github.com/Taiwo703/API-project.git · scanned 2026-05-28 14:23 UTC (1 week, 1 day ago) · 10 languages

35 findings (11 legacy + 24 scanner) 14th percentile · Javascript · tiny (<2K LoC) Scanner says 76 (lower by 30)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 1 day ago · v3 · 19 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	50.0	0.15	7.50
`security_score`	94.3	0.25	23.57
`testing_score`	0.0	0.20	0.00
`documentation_score`	10.0	0.15	1.50
`practices_score`	32.0	0.15	4.80
`code_quality`	80.0	0.10	8.00
Overall		1.00	45.4

Severity distribution — click a segment to filter

Active filters: severity: low × excluding tests × Reset all

Severity: Critical 0 High 2 Medium 6 Low 6 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 11 9-layer 8 Crowd 0 Layer: Quality 7 Security 5 Software 2 Frontend 2 Cicd 1 Api 2

Exclude dismissed / FP Exclude test files

Scan summary Repository scanned at 75.8/100 with 77.8% coverage. It contains 8 nodes across 2 cross-layer flows, written primarily in mixed languages. Engine surfaced 8 findings — concentrated in frontend (2), api (2), software (1). Risk profile is low: 0 critical, 0 high, 3 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 6 of 19 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

low Legacy security auth conf 0.76 [AUC005] No authorization-focused tests detected: No test files with common authorization, ownership, 403, admin, or super_admin assertions were found.

No test files with common authorization, ownership, 403, admin, or super_admin assertions were found.

authlegacy

low Legacy quality documentation No LICENSE file

Add a LICENSE file to your repository. Use choosealicense.com to pick the right license (MIT for permissive, Apache 2.0 for patent protection, GPL for copyleft).

documentationlegacy

low 9-layer software dead-code-candidate conf 1.00 File has no detected symbols: app.js

Source file with no class/function declarations — possible config, dead code, or scratch file.

dead-code-candidate

low 9-layer frontend frontend-quality conf 1.00 Stray `console.log` in TS/JS — app.js:18

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

frontend-qualityfq.console-leak

low 9-layer api wiring conf 1.00 Unused endpoint: GET /api/v1/products

`app.js` declares `GET /api/v1/products` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /api/v1/products/:id

`app.js` declares `GET /api/v1/products/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

wiringunused-endpoint

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/4c680485-cbd6-4f92-8a13-181a1478b4a9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4c680485-cbd6-4f92-8a13-181a1478b4a9/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.