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.

rakshitsegwal/renonym-react

https://github.com/rakshitsegwal/renonym-react · scanned 2026-06-16 04:37 UTC (1 month, 3 weeks ago)

57 raw signals (0 security + 57 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 3 weeks ago · v1 · 57 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 57 findings

Severity distribution — click a segment to filter

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

Severity: Critical 0 High 4 Medium 6 Low 45 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 57 Crowd 0 Layer: Frontend 6 Network 1 Quality 10 Api 40

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 72.3/100 with 88.9% coverage. It contains 144 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 57 findings — concentrated in api (40), quality (10), frontend (6). Risk profile is high: 0 critical, 4 high, 6 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.linkedin.com/v2/userinfo (server.js:1754)

`server.js:1754` calls `GET https://api.linkedin.com/v2/userinfo` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.linkedin.com/v2/userinfo` If this points at an external API, prefix it with `https://` so t…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.googleapis.com/oauth2/v3/userinfo (server.js:1701)

`server.js:1701` calls `GET https://www.googleapis.com/oauth2/v3/userinfo` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.googleapis.com/oauth2/v3/userinfo` If this points at an external API, prefix it wi…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST https://oauth2.googleapis.com/token (server.js:1692)

`server.js:1692` calls `POST https://oauth2.googleapis.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/oauth2.googleapis.com/token` If this points at an external API, prefix it with `https://` so th…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST https://www.linkedin.com/oauth/v2/accessToken (server.js:1744)

`server.js:1744` calls `POST https://www.linkedin.com/oauth/v2/accessToken` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.linkedin.com/oauth/v2/accesstoken` If this points at an external API, prefix it w…

Dangling fetchFetch

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/51436220-ddf3-4d7e-b679-d6fb1e5f96b0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/51436220-ddf3-4d7e-b679-d6fb1e5f96b0/

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.