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.
Sign up free Scan another repo

wenwei4046/2990s

https://github.com/wenwei4046/2990s · scanned 2026-06-16 00:56 UTC (2 months, 1 week ago)

510 raw signals (0 security + 510 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 510 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
71.9
/100
Security checks
72
0 findings
System graph
72
100.0% cov · 510 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 69 Medium 28 Low 110 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 510 Crowd 0 Layer: Frontend 6 Security 2 Cicd 1 Quality 382 Api 119
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 71.9/100 with 100.0% coverage. It contains 6382 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 510 findings — concentrated in quality (382), api (119), frontend (6). Risk profile is high: 0 critical, 69 high, 28 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 207 of 510 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: DELETE /model-free-gifts/${MODEL_ID} (apps/api/src/routes/model-free-gifts.test.ts:330)
`apps/api/src/routes/model-free-gifts.test.ts:330` calls `DELETE /model-free-gifts/${MODEL_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-free-gifts/<p>` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /model-free-gifts/${MODEL_ID} (apps/api/src/routes/model-free-gifts.test.ts:352)
`apps/api/src/routes/model-free-gifts.test.ts:352` calls `DELETE /model-free-gifts/${MODEL_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-free-gifts/<p>` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /model-free-gifts/${MODEL_ID} (apps/api/src/routes/model-free-gifts.test.ts:358)
`apps/api/src/routes/model-free-gifts.test.ts:358` calls `DELETE /model-free-gifts/${MODEL_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-free-gifts/<p>` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /model-free-gifts/${MODEL_ID} (apps/api/src/routes/model-free-gifts.test.ts:366)
`apps/api/src/routes/model-free-gifts.test.ts:366` calls `DELETE /model-free-gifts/${MODEL_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-free-gifts/<p>` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/audit-log (apps/api/src/routes/audit-log.test.ts:116)
`apps/api/src/routes/audit-log.test.ts:116` calls `GET /admin/audit-log` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/audit-log` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/audit-log (apps/api/src/routes/audit-log.test.ts:122)
`apps/api/src/routes/audit-log.test.ts:122` calls `GET /admin/audit-log` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/audit-log` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/audit-log (apps/api/src/routes/audit-log.test.ts:128)
`apps/api/src/routes/audit-log.test.ts:128` calls `GET /admin/audit-log` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/audit-log` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/audit-log (apps/api/src/routes/audit-log.test.ts:137)
`apps/api/src/routes/audit-log.test.ts:137` calls `GET /admin/audit-log` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/audit-log` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/audit-log (apps/api/src/routes/audit-log.test.ts:144)
`apps/api/src/routes/audit-log.test.ts:144` calls `GET /admin/audit-log` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/audit-log` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/audit-log (apps/api/src/routes/audit-log.test.ts:170)
`apps/api/src/routes/audit-log.test.ts:170` calls `GET /admin/audit-log` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/audit-log` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/audit-log (apps/api/src/routes/audit-log.test.ts:198)
`apps/api/src/routes/audit-log.test.ts:198` calls `GET /admin/audit-log` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/audit-log` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/audit-log?amountMin=abc (apps/api/src/routes/audit-log.test.ts:180)
`apps/api/src/routes/audit-log.test.ts:180` calls `GET /admin/audit-log?amountMin=abc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/audit-log` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/audit-log?paymentMethod=credit (apps/api/src/routes/audit-log.test.ts:186)
`apps/api/src/routes/audit-log.test.ts:186` calls `GET /admin/audit-log?paymentMethod=credit` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/audit-log` If this points at an external API, prefix it wit…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /mfg-sales-orders/customer-search?name=${encodeURIComponent(name)} (apps/api/src/routes/mfg-sales-orders.customer-search.test.ts:77)
`apps/api/src/routes/mfg-sales-orders.customer-search.test.ts:77` calls `GET /mfg-sales-orders/customer-search?name=${encodeURIComponent(name)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/mfg-sales-orde…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /model-free-gifts (apps/api/src/routes/model-free-gifts.test.ts:110)
`apps/api/src/routes/model-free-gifts.test.ts:110` calls `GET /model-free-gifts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-free-gifts` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /model-free-gifts (apps/api/src/routes/model-free-gifts.test.ts:146)
`apps/api/src/routes/model-free-gifts.test.ts:146` calls `GET /model-free-gifts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-free-gifts` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /pos/sales-staff (apps/api/src/routes/pos.test.ts:76)
`apps/api/src/routes/pos.test.ts:76` calls `GET /pos/sales-staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/pos/sales-staff` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /pos/sales-staff?showroomId=kl (apps/api/src/routes/pos.test.ts:63)
`apps/api/src/routes/pos.test.ts:63` calls `GET /pos/sales-staff?showroomId=kl` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/pos/sales-staff` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/staff/${TARGET_ID} (apps/api/src/routes/admin.test.ts:479)
`apps/api/src/routes/admin.test.ts:479` calls `PATCH /admin/staff/${TARGET_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff/<p>` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/staff/${TARGET_ID} (apps/api/src/routes/admin.test.ts:489)
`apps/api/src/routes/admin.test.ts:489` calls `PATCH /admin/staff/${TARGET_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff/<p>` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/staff/${TARGET_ID} (apps/api/src/routes/admin.test.ts:500)
`apps/api/src/routes/admin.test.ts:500` calls `PATCH /admin/staff/${TARGET_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff/<p>` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/staff/${TARGET_ID} (apps/api/src/routes/admin.test.ts:510)
`apps/api/src/routes/admin.test.ts:510` calls `PATCH /admin/staff/${TARGET_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff/<p>` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/staff/${TARGET_ID}/pin (apps/api/src/routes/admin.test.ts:280)
`apps/api/src/routes/admin.test.ts:280` calls `PATCH /admin/staff/${TARGET_ID}/pin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff/<p>/pin` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/staff/${TARGET_ID}/pin (apps/api/src/routes/admin.test.ts:289)
`apps/api/src/routes/admin.test.ts:289` calls `PATCH /admin/staff/${TARGET_ID}/pin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff/<p>/pin` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/staff/${TARGET_ID}/pin (apps/api/src/routes/admin.test.ts:299)
`apps/api/src/routes/admin.test.ts:299` calls `PATCH /admin/staff/${TARGET_ID}/pin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff/<p>/pin` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/staff/${TARGET_ID}/pin (apps/api/src/routes/admin.test.ts:321)
`apps/api/src/routes/admin.test.ts:321` calls `PATCH /admin/staff/${TARGET_ID}/pin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff/<p>/pin` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/staff/${TARGET_ID}/pin (apps/api/src/routes/admin.test.ts:345)
`apps/api/src/routes/admin.test.ts:345` calls `PATCH /admin/staff/${TARGET_ID}/pin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff/<p>/pin` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/staff/${TARGET_ID}/pin (apps/api/src/routes/admin.test.ts:355)
`apps/api/src/routes/admin.test.ts:355` calls `PATCH /admin/staff/${TARGET_ID}/pin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff/<p>/pin` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/staff/not-a-uuid/pin (apps/api/src/routes/admin.test.ts:364)
`apps/api/src/routes/admin.test.ts:364` calls `PATCH /admin/staff/not-a-uuid/pin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff/not-a-uuid/pin` If this points at an external API, prefix it with…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/staff (apps/api/src/routes/admin.test.ts:119)
`apps/api/src/routes/admin.test.ts:119` calls `POST /admin/staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/staff (apps/api/src/routes/admin.test.ts:144)
`apps/api/src/routes/admin.test.ts:144` calls `POST /admin/staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/staff (apps/api/src/routes/admin.test.ts:162)
`apps/api/src/routes/admin.test.ts:162` calls `POST /admin/staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/staff (apps/api/src/routes/admin.test.ts:177)
`apps/api/src/routes/admin.test.ts:177` calls `POST /admin/staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/staff (apps/api/src/routes/admin.test.ts:192)
`apps/api/src/routes/admin.test.ts:192` calls `POST /admin/staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/staff (apps/api/src/routes/admin.test.ts:211)
`apps/api/src/routes/admin.test.ts:211` calls `POST /admin/staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/staff (apps/api/src/routes/admin.test.ts:235)
`apps/api/src/routes/admin.test.ts:235` calls `POST /admin/staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/staff (apps/api/src/routes/admin.test.ts:380)
`apps/api/src/routes/admin.test.ts:380` calls `POST /admin/staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/staff (apps/api/src/routes/admin.test.ts:394)
`apps/api/src/routes/admin.test.ts:394` calls `POST /admin/staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/staff (apps/api/src/routes/admin.test.ts:408)
`apps/api/src/routes/admin.test.ts:408` calls `POST /admin/staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/staff (apps/api/src/routes/admin.test.ts:428)
`apps/api/src/routes/admin.test.ts:428` calls `POST /admin/staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/staff (apps/api/src/routes/admin.test.ts:89)
`apps/api/src/routes/admin.test.ts:89` calls `POST /admin/staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/staff` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /mfg-products/${SKU_ID}/activate-one-shot (apps/api/src/routes/mfg-products.test.ts:134)
`apps/api/src/routes/mfg-products.test.ts:134` calls `POST /mfg-products/${SKU_ID}/activate-one-shot` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/mfg-products/<p>/activate-one-shot` If this points at an …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /mfg-products/${SKU_ID}/activate-one-shot (apps/api/src/routes/mfg-products.test.ts:191)
`apps/api/src/routes/mfg-products.test.ts:191` calls `POST /mfg-products/${SKU_ID}/activate-one-shot` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/mfg-products/<p>/activate-one-shot` If this points at an …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /mfg-products/${SKU_ID}/activate-one-shot (apps/api/src/routes/mfg-products.test.ts:199)
`apps/api/src/routes/mfg-products.test.ts:199` calls `POST /mfg-products/${SKU_ID}/activate-one-shot` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/mfg-products/<p>/activate-one-shot` If this points at an …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /mfg-products/${SKU_ID}/activate-one-shot (apps/api/src/routes/mfg-products.test.ts:81)
`apps/api/src/routes/mfg-products.test.ts:81` calls `POST /mfg-products/${SKU_ID}/activate-one-shot` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/mfg-products/<p>/activate-one-shot` If this points at an e…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /pos/pin-login (apps/api/src/routes/pos.test.ts:114)
`apps/api/src/routes/pos.test.ts:114` calls `POST /pos/pin-login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/pos/pin-login` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /pos/pin-login (apps/api/src/routes/pos.test.ts:126)
`apps/api/src/routes/pos.test.ts:126` calls `POST /pos/pin-login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/pos/pin-login` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /pos/pin-login (apps/api/src/routes/pos.test.ts:141)
`apps/api/src/routes/pos.test.ts:141` calls `POST /pos/pin-login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/pos/pin-login` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /pos/pin-login (apps/api/src/routes/pos.test.ts:147)
`apps/api/src/routes/pos.test.ts:147` calls `POST /pos/pin-login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/pos/pin-login` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /pos/pin-login (apps/api/src/routes/pos.test.ts:161)
`apps/api/src/routes/pos.test.ts:161` calls `POST /pos/pin-login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/pos/pin-login` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /pos/pin-login (apps/api/src/routes/pos.test.ts:173)
`apps/api/src/routes/pos.test.ts:173` calls `POST /pos/pin-login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/pos/pin-login` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /pos/pin-login (apps/api/src/routes/pos.test.ts:184)
`apps/api/src/routes/pos.test.ts:184` calls `POST /pos/pin-login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/pos/pin-login` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /pos/pin-login (apps/api/src/routes/pos.test.ts:194)
`apps/api/src/routes/pos.test.ts:194` calls `POST /pos/pin-login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/pos/pin-login` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /slips/${sessionId}/confirm (apps/api/src/routes/slips.test.ts:169)
`apps/api/src/routes/slips.test.ts:169` calls `POST /slips/${sessionId}/confirm` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/slips/<p>/confirm` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /slips/${sessionId}/confirm (apps/api/src/routes/slips.test.ts:182)
`apps/api/src/routes/slips.test.ts:182` calls `POST /slips/${sessionId}/confirm` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/slips/<p>/confirm` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /slips/${sessionId}/confirm (apps/api/src/routes/slips.test.ts:196)
`apps/api/src/routes/slips.test.ts:196` calls `POST /slips/${sessionId}/confirm` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/slips/<p>/confirm` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /slips/${sessionId}/confirm (apps/api/src/routes/slips.test.ts:222)
`apps/api/src/routes/slips.test.ts:222` calls `POST /slips/${sessionId}/confirm` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/slips/<p>/confirm` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /slips/${sessionId}/confirm (apps/api/src/routes/slips.test.ts:245)
`apps/api/src/routes/slips.test.ts:245` calls `POST /slips/${sessionId}/confirm` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/slips/<p>/confirm` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /slips/init (apps/api/src/routes/slips.test.ts:102)
`apps/api/src/routes/slips.test.ts:102` calls `POST /slips/init` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/slips/init` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /slips/init (apps/api/src/routes/slips.test.ts:116)
`apps/api/src/routes/slips.test.ts:116` calls `POST /slips/init` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/slips/init` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /slips/init (apps/api/src/routes/slips.test.ts:86)
`apps/api/src/routes/slips.test.ts:86` calls `POST /slips/init` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/slips/init` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /model-free-gifts (apps/api/src/routes/model-free-gifts.test.ts:161)
`apps/api/src/routes/model-free-gifts.test.ts:161` calls `PUT /model-free-gifts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-free-gifts` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /model-free-gifts (apps/api/src/routes/model-free-gifts.test.ts:173)
`apps/api/src/routes/model-free-gifts.test.ts:173` calls `PUT /model-free-gifts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-free-gifts` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /model-free-gifts (apps/api/src/routes/model-free-gifts.test.ts:208)
`apps/api/src/routes/model-free-gifts.test.ts:208` calls `PUT /model-free-gifts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-free-gifts` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /model-free-gifts (apps/api/src/routes/model-free-gifts.test.ts:236)
`apps/api/src/routes/model-free-gifts.test.ts:236` calls `PUT /model-free-gifts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-free-gifts` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /model-free-gifts (apps/api/src/routes/model-free-gifts.test.ts:259)
`apps/api/src/routes/model-free-gifts.test.ts:259` calls `PUT /model-free-gifts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-free-gifts` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /model-free-gifts (apps/api/src/routes/model-free-gifts.test.ts:271)
`apps/api/src/routes/model-free-gifts.test.ts:271` calls `PUT /model-free-gifts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-free-gifts` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /model-free-gifts (apps/api/src/routes/model-free-gifts.test.ts:283)
`apps/api/src/routes/model-free-gifts.test.ts:283` calls `PUT /model-free-gifts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-free-gifts` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /model-free-gifts (apps/api/src/routes/model-free-gifts.test.ts:295)
`apps/api/src/routes/model-free-gifts.test.ts:295` calls `PUT /model-free-gifts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-free-gifts` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — prototype/pos-configurator.jsx:205
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/api/src/lib/r2.ts:214
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/api/src/middleware/auth.ts:17
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/api/src/routes/mfg-sales-orders.ts:1036
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/api/src/routes/mrp.ts:306
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/backend/src/lib/authed-fetch.ts:80
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/backend/src/lib/product-models-queries.ts:268
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/backend/src/lib/slip.ts:94
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/backend/src/lib/verified-save.ts:86
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/backend/src/pages/ConsignmentOrders.tsx:937
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/backend/src/pages/MfgDeliveryOrdersList.tsx:489
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/backend/src/pages/MfgSalesOrdersList.tsx:940
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/backend/src/pages/SalesInvoicesList.tsx:450
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/pos/src/lib/customer-search.ts:87
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/pos/src/lib/personal-quick-picks.ts:54
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/pos/src/lib/products/mfg-products-queries.ts:604
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/pos/src/lib/products/product-models-queries.ts:223
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/pos/src/lib/queries.ts:42
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/pos/src/lib/quotes.ts:53
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/pos/src/lib/slip.ts:50
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/pos/src/lib/so-doc.ts:120
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/pos/src/lib/staff.ts:87
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/pos/src/pages/Catalog.tsx:196
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/pos/src/pages/OrderStatus.tsx:223
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in prototype/pos-configurator.jsx:205
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
prototype/pos-configurator.jsx:205 Dangerous innerhtml
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 527 placeholder/mock markers across 121 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 10 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ALLOW_LOCAL_API_URL`, `DB_PWD`, `DRY_RUN`, `MIG_FILE`, `SUPABASE_DB_URL`, `TBL`, `VITE_API_URL`, `VITE_BACKEND_PORTAL_URL` + 2 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 20 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph security security conf 1.00 Insecure pattern 'document_write' in prototype/backend-drawer.jsx:108
Found a known-risky pattern (document_write). Review and replace if possible.
prototype/backend-drawer.jsx:108 Document write
low System graph quality Tests conf 1.00 Low test-to-source ratio
77 tests / 450 src (ratio 0.17).
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/api/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/api/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/backend/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/backend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/pos/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/pos/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/db/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/db/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/design-system/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/design-system/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/shared/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/shared/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `useLegacy` in apps/api/src/routes/mrp.ts:472
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/api/src/index.ts:180
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
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/api/src/routes/mfg-sales-orders.ts:896
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
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/db/scripts/backfill-so-line-cost.ts:123
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
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:id
`apps/api/src/routes/sofa-combos.ts` declares `DELETE /: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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:id/bindings/:bindingId
`apps/api/src/routes/suppliers.ts` declares `DELETE /:id/bindings/:bindingId` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:id/items/:itemId
`apps/api/src/routes/consignment-notes.ts` declares `DELETE /:id/items/:itemId` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:id/payments/:paymentId
`apps/api/src/routes/consignment-notes.ts` declares `DELETE /:id/payments/:paymentId` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /changes/:id
`apps/api/src/routes/maintenance-config.ts` declares `DELETE /changes/: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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`apps/api/src/routes/sofa-combos.ts` declares `GET /` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:id
`apps/api/src/routes/consignment-notes.ts` declares `GET /: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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:id/bindings
`apps/api/src/routes/suppliers.ts` declares `GET /:id/bindings` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:id/linked
`apps/api/src/routes/purchase-consignment-orders.ts` declares `GET /:id/linked` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:id/payments
`apps/api/src/routes/consignment-notes.ts` declares `GET /:id/payments` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:id/scorecard
`apps/api/src/routes/suppliers.ts` declares `GET /:id/scorecard` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /accounts
`apps/api/src/routes/accounting.ts` declares `GET /accounts` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /ap-aging
`apps/api/src/routes/accounting.ts` declares `GET /ap-aging` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /ar-aging
`apps/api/src/routes/accounting.ts` declares `GET /ar-aging` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /balances
`apps/api/src/routes/accounting.ts` declares `GET /balances` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /deliverable-order-lines
`apps/api/src/routes/consignment-notes.ts` declares `GET /deliverable-order-lines` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /deliverable-so-lines
`apps/api/src/routes/delivery-orders-mfg.ts` declares `GET /deliverable-so-lines` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /gl
`apps/api/src/routes/accounting.ts` declares `GET /gl` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /history
`apps/api/src/routes/sofa-combos.ts` declares `GET /history` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /journal-entries
`apps/api/src/routes/accounting.ts` declares `GET /journal-entries` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /journal-entries/:id
`apps/api/src/routes/accounting.ts` declares `GET /journal-entries/: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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /material/:kind/:code
`apps/api/src/routes/suppliers.ts` declares `GET /material/:kind/:code` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /resolved
`apps/api/src/routes/maintenance-config.ts` declares `GET /resolved` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /returnable-note-lines
`apps/api/src/routes/consignment-returns.ts` declares `GET /returnable-note-lines` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:id
`apps/api/src/routes/consignment-notes.ts` declares `PATCH /: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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:id/active
`apps/api/src/routes/fabric-tracking.ts` declares `PATCH /:id/active` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:id/bindings/:bindingId
`apps/api/src/routes/suppliers.ts` declares `PATCH /:id/bindings/:bindingId` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:id/description
`apps/api/src/routes/fabric-tracking.ts` declares `PATCH /:id/description` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:id/items/:itemId
`apps/api/src/routes/consignment-notes.ts` declares `PATCH /:id/items/:itemId` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:id/series
`apps/api/src/routes/fabric-tracking.ts` declares `PATCH /:id/series` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:id/status
`apps/api/src/routes/consignment-notes.ts` declares `PATCH /:id/status` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:id/submit
`apps/api/src/routes/purchase-consignment-orders.ts` declares `PATCH /:id/submit` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:id/supplier-code
`apps/api/src/routes/fabric-tracking.ts` declares `PATCH /:id/supplier-code` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:id/tier
`apps/api/src/routes/fabric-tracking.ts` declares `PATCH /:id/tier` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`apps/api/src/routes/sofa-combos.ts` declares `POST /` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /:id/bindings
`apps/api/src/routes/suppliers.ts` declares `POST /:id/bindings` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /:id/bindings/batch
`apps/api/src/routes/suppliers.ts` declares `POST /:id/bindings/batch` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /:id/items
`apps/api/src/routes/consignment-notes.ts` declares `POST /:id/items` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /:id/payments
`apps/api/src/routes/consignment-notes.ts` declares `POST /:id/payments` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /bulk-upsert
`apps/api/src/routes/fabric-tracking.ts` declares `POST /bulk-upsert` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /changes
`apps/api/src/routes/maintenance-config.ts` declares `POST /changes` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /from-sos
`apps/api/src/routes/delivery-orders-mfg.ts` declares `POST /from-sos` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /journal-entries
`apps/api/src/routes/accounting.ts` declares `POST /journal-entries` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /journal-entries/:id/post
`apps/api/src/routes/accounting.ts` declares `POST /journal-entries/:id/post` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /post/pi/:invoiceNumber
`apps/api/src/routes/accounting.ts` declares `POST /post/pi/:invoiceNumber` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /post/si/:invoiceNumber
`apps/api/src/routes/accounting.ts` declares `POST /post/si/:invoiceNumber` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /sofa-compartments/rename
`apps/api/src/routes/maintenance-config.ts` declares `POST /sofa-compartments/rename` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /
`apps/api/src/routes/pos-cart.ts` declares `PUT /` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /:id
`apps/api/src/routes/sofa-combos.ts` declares `PUT /: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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /slips/*
`apps/api/src/index.ts` declares `USE /slips/*` 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.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: apps/api/src/routes/consignment-orders.ts (1950 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/src/routes/delivery-orders-mfg.ts (2355 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/src/routes/delivery-returns.ts (1317 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/src/routes/grns.ts (1815 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/src/routes/mfg-purchase-orders.ts (1911 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/src/routes/mfg-sales-orders.ts (6758 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/src/routes/purchase-consignment-receives.ts (1154 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/src/routes/purchase-consignment-returns.ts (952 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/src/routes/purchase-invoices.ts (1077 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/src/routes/purchase-returns.ts (1106 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/src/routes/sales-invoices.ts (1189 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/src/routes/scan-so.ts (1475 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/components/DataGrid.tsx (1154 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/components/SoLineCard.tsx (1415 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/lib/flow-queries.ts (1974 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/pages/ConsignmentOrders.tsx (1717 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/pages/DeliveryOrderDetail.tsx (1208 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/pages/GrnNew.tsx (1100 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/pages/Inventory.tsx (1486 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/pages/MfgSalesOrdersList.tsx (1742 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/pages/Mrp.tsx (1204 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/pages/ProductModelDetail.tsx (1331 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/pages/ProductModels.tsx (2152 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/pages/Products.tsx (4752 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/pages/PurchaseOrderNew.tsx (1347 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/pages/SalesOrderDetail.tsx (2576 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/pages/SalesOrderMaintenance.tsx (1529 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/pages/SalesOrderNew.tsx (1298 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/pages/SupplierDetail.tsx (3807 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/pos/src/lib/queries.ts (2439 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/pos/src/pages/Configurator.tsx (2974 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/pos/src/pages/CustomBuilder.tsx (2038 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/pos/src/pages/OrderStatus.tsx (1995 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/pos/src/pages/Products.tsx (5993 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/pos/src/pages/SalesOrderMaintenance.tsx (1433 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/db/src/schema.ts (2798 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/shared/src/__tests__/sofa-build.test.ts (1321 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/shared/src/sofa-build.ts (1651 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: prototype/backend-catalog.jsx (1034 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: prototype/pos-configurator.jsx (1261 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: prototype/pos-handover.jsx (1262 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: prototype/pos-sofa-config.jsx (2074 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/64e2a192-2e64-4a58-9de3-2fff1949c65e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/64e2a192-2e64-4a58-9de3-2fff1949c65e/

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.