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

rocketlang/ankrshield

https://github.com/rocketlang/ankrshield · scanned 2026-06-15 23:54 UTC (2 months, 3 weeks ago)

338 raw signals (0 security + 338 graph)

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

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 311 actionable findings from 1 signal source. 27 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
40.9
/100
Security checks
41
0 findings
System graph
41
100.0% cov · 311 findings
Critical
2
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 2 High 38 Medium 48 Low 145 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 311 Crowd 0 Layer: Frontend 85 Hardware 3 Security 27 Cicd 4 Quality 107 Api 85
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 40.9/100 with 100.0% coverage. It contains 3075 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 338 findings — concentrated in quality (119), frontend (85), api (85). Risk profile is high: 3 critical, 38 high, 64 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 231 of 311 actionable findings. 338 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 Possible secret in packages/ai-warrior/src/defense/honeypot.ts
Detected pattern matching github_token. Rotate the credential and move to a secret manager.
packages/ai-warrior/src/defense/honeypot.ts:50
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/auth/api-keys/${id} (apps/web/src/pages/ApiKeys.tsx:433)
`apps/web/src/pages/ApiKeys.tsx:433` calls `DELETE /api/auth/api-keys/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/api-keys/<p>` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/billing/portal?apiKeyId=${encodeURIComponent(apiKeyId)} (apps/web/src/pages/ApiKeys.tsx:260)
`apps/web/src/pages/ApiKeys.tsx:260` calls `GET /api/billing/portal?apiKeyId=${encodeURIComponent(apiKeyId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/portal` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/some/other/path (apps/desktop/src/main/__tests__/aegis-proxy-wa-inbound.test.ts:395)
`apps/desktop/src/main/__tests__/aegis-proxy-wa-inbound.test.ts:395` calls `GET http://127.0.0.1:${port}/some/other/path` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/some/other/path` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://${domain}/favicon.ico (packages/risk-intelligence/src/detectors/social-brand-monitor.ts:217)
`packages/risk-intelligence/src/detectors/social-brand-monitor.ts:217` calls `GET https://${domain}/favicon.ico` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>/favicon.ico` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.abuseipdb.com/api/v2/check?ipAddress=${encodeURIComponent(ip)}&maxAgeInDays=30 (apps/api/src/main.ts:414)
`apps/api/src/main.ts:414` calls `GET https://api.abuseipdb.com/api/v2/check?ipAddress=${encodeURIComponent(ip)}&maxAgeInDays=30` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.abuseipdb.com/api/v2/check`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/search/code?q=${encodeURIComponent(q)}&per_page=5 (apps/api/src/xshield/risk-engine.ts:508)
`apps/api/src/xshield/risk-engine.ts:508` calls `GET https://api.github.com/search/code?q=${encodeURIComponent(q)}&per_page=5` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/search/code` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.greynoise.io/v3/community/${ip} (apps/api/src/xshield/risk-engine.ts:323)
`apps/api/src/xshield/risk-engine.ts:323` calls `GET https://api.greynoise.io/v3/community/${ip}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.greynoise.io/v3/community/<p>` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.npmjs.org/downloads/point/last-month/${encodeURIComponent(pkg.name)} (packages/risk-intelligence/src/detectors/supply-chain-scanner.ts:404)
`packages/risk-intelligence/src/detectors/supply-chain-scanner.ts:404` calls `GET https://api.npmjs.org/downloads/point/last-month/${encodeURIComponent(pkg.name)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.shodan.io/shodan/host/${ip}?key=${process.env.SHODAN_API_KEY} (apps/api/src/xshield/risk-engine.ts:600)
`apps/api/src/xshield/risk-engine.ts:600` calls `GET https://api.shodan.io/shodan/host/${ip}?key=${process.env.SHODAN_API_KEY}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.shodan.io/shodan/host/<p>` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://crt.sh/?q=${encodedEmail}&output=json (apps/api/src/xshield/risk-engine.ts:927)
`apps/api/src/xshield/risk-engine.ts:927` calls `GET https://crt.sh/?q=${encodedEmail}&output=json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/crt.sh` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://crt.sh/?q=${encodeURIComponent(domain)}&output=json (apps/api/src/xshield/risk-engine.ts:282)
`apps/api/src/xshield/risk-engine.ts:282` calls `GET https://crt.sh/?q=${encodeURIComponent(domain)}&output=json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/crt.sh` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://haveibeenpwned.com/api/v3/breaches (apps/api/src/xshield/risk-engine.ts:362)
`apps/api/src/xshield/risk-engine.ts:362` calls `GET https://haveibeenpwned.com/api/v3/breaches` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/haveibeenpwned.com/api/v3/breaches` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://openphish.com/feed.txt (apps/api/src/xshield/risk-engine.ts:446)
`apps/api/src/xshield/risk-engine.ts:446` calls `GET https://openphish.com/feed.txt` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/openphish.com/feed.txt` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://otx.alienvault.com/api/v1/indicators/domain/${encodeURIComponent(domain)}/general (apps/api/src/xshield/risk-engine.ts:552)
`apps/api/src/xshield/risk-engine.ts:552` calls `GET https://otx.alienvault.com/api/v1/indicators/domain/${encodeURIComponent(domain)}/general` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/otx.alienvault.co…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://pypi.org/pypi/${encodeURIComponent(name)}/json (apps/api/src/main.ts:3929)
`apps/api/src/main.ts:3929` calls `GET https://pypi.org/pypi/${encodeURIComponent(name)}/json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/pypi.org/pypi/<p>/json` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://pypi.org/pypi/${encodeURIComponent(pkg.name)}/json (packages/risk-intelligence/src/detectors/supply-chain-scanner.ts:536)
`packages/risk-intelligence/src/detectors/supply-chain-scanner.ts:536` calls `GET https://pypi.org/pypi/${encodeURIComponent(pkg.name)}/json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/pypi.org/pypi/<p>/j…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://registry.npmjs.org/${encoded} (apps/api/src/main.ts:3899)
`apps/api/src/main.ts:3899` calls `GET https://registry.npmjs.org/${encoded}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/registry.npmjs.org/<p>` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://registry.npmjs.org/${encodeURIComponent(pkg.name)} (packages/risk-intelligence/src/detectors/supply-chain-scanner.ts:399)
`packages/risk-intelligence/src/detectors/supply-chain-scanner.ts:399` calls `GET https://registry.npmjs.org/${encodeURIComponent(pkg.name)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/registry.npmjs.org/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://urlscan.io/api/v1/search/?q=domain:${encodeURIComponent(domain)}&size=5 (apps/api/src/xshield/risk-engine.ts:404)
`apps/api/src/xshield/risk-engine.ts:404` calls `GET https://urlscan.io/api/v1/search/?q=domain:${encodeURIComponent(domain)}&size=5` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/urlscan.io/api/v1/search` I…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.virustotal.com/api/v3/files/${sha256.toLowerCase()} (apps/api/src/main.ts:4690)
`apps/api/src/main.ts:4690` calls `GET https://www.virustotal.com/api/v3/files/${sha256.toLowerCase()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.virustotal.com/api/v3/files/<p>` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/billing/checkout (apps/web/src/pages/ApiKeys.tsx:232)
`apps/web/src/pages/ApiKeys.tsx:232` calls `POST /api/billing/checkout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/checkout` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/login (apps/web/src/lib/apiClient.ts:59)
`apps/web/src/lib/apiClient.ts:59` calls `POST /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/register (apps/web/src/lib/apiClient.ts:52)
`apps/web/src/lib/apiClient.ts:52` calls `POST /auth/register` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/register` 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 http://127.0.0.1:${port}/webhook/whatsapp (apps/desktop/src/main/__tests__/aegis-proxy-wa-inbound.test.ts:301)
`apps/desktop/src/main/__tests__/aegis-proxy-wa-inbound.test.ts:301` calls `POST http://127.0.0.1:${port}/webhook/whatsapp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/webhook/whatsapp` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/webhook/whatsapp (apps/desktop/src/main/__tests__/aegis-proxy-wa-inbound.test.ts:333)
`apps/desktop/src/main/__tests__/aegis-proxy-wa-inbound.test.ts:333` calls `POST http://127.0.0.1:${port}/webhook/whatsapp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/webhook/whatsapp` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/webhook/whatsapp (apps/desktop/src/main/__tests__/aegis-proxy-wa-inbound.test.ts:370)
`apps/desktop/src/main/__tests__/aegis-proxy-wa-inbound.test.ts:370` calls `POST http://127.0.0.1:${port}/webhook/whatsapp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/webhook/whatsapp` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/webhook/whatsapp (apps/desktop/src/main/__tests__/aegis-proxy-wa-inbound.test.ts:384)
`apps/desktop/src/main/__tests__/aegis-proxy-wa-inbound.test.ts:384` calls `POST http://127.0.0.1:${port}/webhook/whatsapp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/webhook/whatsapp` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.abuseipdb.com/api/v2/report (apps/api/src/main.ts:2257)
`apps/api/src/main.ts:2257` calls `POST https://api.abuseipdb.com/api/v2/report` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.abuseipdb.com/api/v2/report` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (packages/risk-intelligence/src/threat-narrative.ts:162)
`packages/risk-intelligence/src/threat-narrative.ts:162` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.osv.dev/v1/querybatch (packages/risk-intelligence/src/detectors/supply-chain-scanner.ts:327)
`packages/risk-intelligence/src/detectors/supply-chain-scanner.ts:327` calls `POST https://api.osv.dev/v1/querybatch` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.osv.dev/v1/querybatch` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${botToken}/sendMessage (apps/api/src/integrations/alert-dispatcher.ts:97)
`apps/api/src/integrations/alert-dispatcher.ts:97` calls `POST https://api.telegram.org/bot${botToken}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://events.pagerduty.com/v2/enqueue (apps/api/src/integrations/alert-dispatcher.ts:152)
`apps/api/src/integrations/alert-dispatcher.ts:152` calls `POST https://events.pagerduty.com/v2/enqueue` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/events.pagerduty.com/v2/enqueue` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://threatfox-api.abuse.ch/api/v1/ (packages/risk-intelligence/src/detectors/qr-detector.ts:169)
`packages/risk-intelligence/src/detectors/qr-detector.ts:169` calls `POST https://threatfox-api.abuse.ch/api/v1/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/threatfox-api.abuse.ch/api/v1` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://threatfox-api.abuse.ch/api/v1/ (packages/risk-intelligence/src/detectors/social-c2-detector.ts:71)
`packages/risk-intelligence/src/detectors/social-c2-detector.ts:71` calls `POST https://threatfox-api.abuse.ch/api/v1/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/threatfox-api.abuse.ch/api/v1` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT http://127.0.0.1:${port}/webhook/whatsapp (apps/desktop/src/main/__tests__/aegis-proxy-wa-inbound.test.ts:400)
`apps/desktop/src/main/__tests__/aegis-proxy-wa-inbound.test.ts:400` calls `PUT http://127.0.0.1:${port}/webhook/whatsapp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/webhook/whatsapp` If thi…
Dangling fetchFetch
high System graph cicd CI/CD security conf 1.00 GitHub Action tracks a moving branch
snyk/actions/node@master can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/ci.yml:175 CI/CD securitySupply chainGithub actions
high System graph security security conf 1.00 Insecure pattern 'exec_used' in apps/desktop/src/main/aegis-proxy/app-identifier.ts:68
Found a known-risky pattern (exec_used). Review and replace if possible.
apps/desktop/src/main/aegis-proxy/app-identifier.ts:68 Exec used
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: apps/web/.env.production
`apps/web/.env.production` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.
apps/web/.env.production ConfigEnv fileRuntime env
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/api/scripts/run-scan-chain.mjs:14
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/integrations/alert-dispatcher.ts:117
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/main.ts:2257
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/desktop/src/main/__tests__/aegis-proxy-wa-inbound.test.ts:286
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/mobile-ios/src/services/NetworkService.ts:37
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/mobile-ios/src/services/PrivacyService.ts:75
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/mobile-ios/src/services/WarriorService.ts:7
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/web/src/lib/apiClient.ts:31
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/web/src/lib/ssoClient.ts:41
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/web/src/pages/ApiKeys.tsx:408
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/web/src/pages/Developers.tsx:141
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/web/src/pages/Onboarding.tsx:251
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/web/src/pages/Setup.tsx:224
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/web/src/pages/SupplyChain.tsx:168
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/xshieldai-asm-ai-module/src/probes/runner.ts:130
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 — packages/ai-warrior/src/llm/client.ts:82
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 authority lacks a verifier contract: apps/xshield-active-api/.claude/settings.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
apps/xshield-active-api/.claude/settings.json VerificationClaude instruction
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 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 hardware Security conf 1.00 Dockerfile runs as root: docker/postgres/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 4 occurrences Frontend route `/evidence` has no Link/navigate to it — apps/web/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
4 occurrences
repo-level (4 hits)
Orphan pageWiring
medium System graph quality Integrity conf 1.00 10 occurrences Frontend route `dashboard` has no Link/navigate to it — apps/desktop/src/renderer/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
10 occurrences
repo-level (10 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 5 occurrences GitHub Action is tag-pinned rather than SHA-pinned
pnpm/action-setup@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 24, 64, 112, 126, 148
.github/workflows/ci.yml:24, 64, 112, 126, 148 (5 hits)
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in apps/api/src/main.ts:4210
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
apps/api/src/main.ts:4210 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in packages/dns-resolver/src/service.ts:87
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
packages/dns-resolver/src/service.ts:87 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in apps/desktop/src/renderer/app.js:54
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
apps/desktop/src/renderer/app.js:54 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in apps/web/public/capabilities.html:134
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
apps/web/public/capabilities.html:134 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in apps/web/public/privacy.html:105
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
apps/web/public/privacy.html:105 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in apps/web/src/pages/VerifyMagicLink.tsx:58
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
apps/web/src/pages/VerifyMagicLink.tsx:58 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in apps/web/src/stores/authStore.ts:57
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
apps/web/src/stores/authStore.ts:57 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/api/src/main.ts:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/api/src/main.ts:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/desktop/src/main/aegis-proxy/app-identifier.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/desktop/src/main/aegis-proxy/app-identifier.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/desktop/src/main/infrastructure/permissions.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/desktop/src/main/infrastructure/permissions.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/xshieldai-varuna/src/report/routes.ts:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/xshieldai-varuna/src/report/routes.ts:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/network-monitor/src/classification/app-resolver.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/network-monitor/src/classification/app-resolver.ts:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/network-monitor/src/monitor/linux-monitor.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/network-monitor/src/monitor/linux-monitor.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/network-monitor/src/monitor/macos-monitor.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/network-monitor/src/monitor/macos-monitor.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/network-monitor/src/monitor/windows-monitor.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/network-monitor/src/monitor/windows-monitor.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/spyware-detector/src/detectors/cve-detector.ts:28
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/spyware-detector/src/detectors/cve-detector.ts:28 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/spyware-detector/src/detectors/linux-rootkit-detector.ts:24
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/spyware-detector/src/detectors/linux-rootkit-detector.ts:24 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/spyware-detector/src/detectors/process-detector.ts:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/spyware-detector/src/detectors/process-detector.ts:20 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/spyware-detector/src/detectors/yara-detector.ts:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/spyware-detector/src/detectors/yara-detector.ts:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/p2-exit-check.ts:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/p2-exit-check.ts:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/p3-exit-check.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/p3-exit-check.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in packages/spyware-detector/src/live-ioc-feed.ts:256
Found a known-risky pattern (weak_hash). Review and replace if possible.
packages/spyware-detector/src/live-ioc-feed.ts:256 Weak hash
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 181 placeholder/mock markers across 71 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Maintenance conf 1.00 36 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph quality Integrity conf 1.00 37 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ABUSEIPDB_API_KEY`, `ADMIN_TOKEN`, `ALERT_EMAIL_WEBHOOK`, `ANKR_AI_PROXY_URL`, `ANKR_WIRE_REST_URL`, `API_URL`, `APK_PATH`, `APK_RELEASE_URL` + 29 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 573 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: timescale/timescaledb-ha:pg15-latest
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker/postgres/Dockerfile:3 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 11 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 16, 19, 34, 56, 59, 104, 107, 140, +3 more
.github/workflows/ci.yml:16, 19, 34, 56, 59, 104, 107, 140, +3 more (11 hits)
CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/desktop/src/renderer/components/Settings.tsx:89
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/web/src/pages/MdmAdmin.tsx:654
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Tests conf 1.00 Low test-to-source ratio
66 tests / 509 src (ratio 0.13).
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/desktop/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/desktop/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/mobile-ios/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/mobile-ios/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/web/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/web/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/xshield-active-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/xshield-active-api/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/xshieldai-varuna/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/xshieldai-varuna/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/ai-governance/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/ai-governance/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/ai-warrior/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/ai-warrior/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/ankrshield-mdm-bridge/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/ankrshield-mdm-bridge/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/api-client/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/api-client/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/config/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/config/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/core/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/core/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/crypto/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/crypto/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/dns-resolver/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/dns-resolver/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/dpdp-scanner/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/dpdp-scanner/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/network-monitor/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/network-monitor/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/policy-engine/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/policy-engine/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/privacy-engine/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/privacy-engine/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/risk-intelligence/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/risk-intelligence/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/sms-shield/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/sms-shield/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/spyware-detector/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/spyware-detector/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/tracker-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/tracker-db/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/ui/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/ui/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `ankrshield_mdm_v1` in apps/mobile-ios/src/mdm/policy-engine.ts:54
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 quality Integrity conf 1.00 Old/deprecated-named symbol `ankrshield_mdm_v1` in apps/mobile-ios/src/mdm/types.ts:42
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 quality Integrity conf 1.00 Old/deprecated-named symbol `wallet_backup` in packages/ai-warrior/src/defense/honeypot.ts:56
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/main.ts:138
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/monitor/traffic-monitor.ts:82
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/warrior/wire-publisher.ts:107
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/xshield/watch-poller.ts:33
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/desktop/src/main/aegis-proxy/dan-inbound-poller.ts:97
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/desktop/src/main/aegis-proxy/ipc-handlers.ts:855
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/desktop/src/main/aegis-proxy/server.ts:103
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/desktop/src/main/aegis-proxy/wa-inbound-webhook-server.ts:108
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/desktop/src/main/auto-launch.ts:23
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/desktop/src/main/index.ts:56
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/desktop/src/main/infrastructure/database.ts:54
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/desktop/src/main/infrastructure/redis.ts:64
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/desktop/src/main/infrastructure/user.ts:53
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/desktop/src/main/ipc.ts:21
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/desktop/src/main/ipc/handlers.ts:76
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/desktop/src/main/services/dns.ts:58
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/desktop/src/main/services/network.ts:79
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/desktop/src/main/services/privacy.ts:80
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/desktop/src/main/services/service-manager.ts:90
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/desktop/src/main/services/settings.ts:184
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/desktop/src/main/updater.ts:17
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/desktop/src/renderer/app.js:8
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/desktop/test-services.ts:10
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/mobile-ios/android/build-tracker-db.js:274
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/mobile-ios/src/hooks/useBlocklist.ts:145
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/warrior-cli/src/commands/scan.ts:17
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/warrior-cli/src/commands/setup.ts:5
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/warrior-cli/src/commands/start.ts:7
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/warrior-cli/src/commands/status.ts:7
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/web/src/pages/Developers.tsx:149
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/ai-warrior/src/warrior.ts:12
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/core/src/cache/redis.ts:25
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/dns-resolver/scripts/cache-metrics.ts:15
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/dns-resolver/scripts/comprehensive-test.ts:31
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/dns-resolver/scripts/download-blocklists.ts:56
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/dns-resolver/scripts/import-to-database.ts:58
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/dns-resolver/scripts/parse-blocklists.ts:154
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/dns-resolver/scripts/test-full-resolver.ts:15
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/dns-resolver/scripts/test-logger.ts:15
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/dns-resolver/scripts/test-lookup.ts:13
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/dns-resolver/src/blocklist/manager.ts:28
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/dns-resolver/src/cache/dns-cache.ts:50
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/dns-resolver/src/logger/dns-logger.ts:165
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/dns-resolver/src/service.ts:200
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/network-monitor/scripts/run-tests.ts:13
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/network-monitor/scripts/test-capture.ts:11
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/network-monitor/scripts/test-integration.ts:11
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/network-monitor/src/monitor/linux-monitor.ts:109
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/network-monitor/src/monitor/macos-monitor.ts:70
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/network-monitor/src/monitor/windows-monitor.ts:79
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/privacy-engine/scripts/import-trackers.ts:24
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/privacy-engine/scripts/run-tests.ts:10
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/privacy-engine/scripts/test-privacy-scoring.ts:7
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 — prisma/seed.ts:17
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 — scripts/p2-exit-check.ts:308
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 — scripts/p3-exit-check.ts:255
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 — scripts/test-db-connection.js:22
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 /account
`apps/api/src/main.ts` declares `DELETE /account` 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 /integrations/email
`apps/api/src/main.ts` declares `DELETE /integrations/email` 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 /integrations/pagerduty
`apps/api/src/main.ts` declares `DELETE /integrations/pagerduty` 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 /integrations/telegram
`apps/api/src/main.ts` declares `DELETE /integrations/telegram` 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/main.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 /account/data-summary
`apps/api/src/main.ts` declares `GET /account/data-summary` 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 /account/export
`apps/api/src/main.ts` declares `GET /account/export` 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 /api/feature-requests
`apps/api/src/main.ts` declares `GET /api/feature-requests` 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 /api/v1/iacs/matrix
`apps/xshieldai-varuna/src/iacs/routes.ts` declares `GET /api/v1/iacs/matrix` 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 /api/v1/pentest/scopes
`apps/xshieldai-varuna/src/pentest/routes.ts` declares `GET /api/v1/pentest/scopes` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/posture
`apps/xshieldai-varuna/src/posture/routes.ts` declares `GET /api/v1/posture` 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 /api/v1/taxii/status
`apps/xshieldai-varuna/src/taxii/routes.ts` declares `GET /api/v1/taxii/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: GET /api/v2/capabilities
`apps/api/src/main.ts` declares `GET /api/v2/capabilities` 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 /api/v2/capabilities/honesty
`apps/api/src/main.ts` declares `GET /api/v2/capabilities/honesty` 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 /api/v2/capabilities/privacy-stats
`apps/api/src/main.ts` declares `GET /api/v2/capabilities/privacy-stats` 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 /api/v2/forja/proof
`apps/api/src/main.ts` declares `GET /api/v2/forja/proof` 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 /api/v2/forja/state
`apps/api/src/main.ts` declares `GET /api/v2/forja/state` 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 /billing/plans
`apps/api/src/main.ts` declares `GET /billing/plans` 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 /brand/report
`apps/api/src/main.ts` declares `GET /brand/report` 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 /device/stats
`apps/api/src/main.ts` declares `GET /device/stats` 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 /download/ankrshield-debug.apk
`apps/api/src/main.ts` declares `GET /download/ankrshield-debug.apk` 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 /download/ankrshield.apk
`apps/api/src/main.ts` declares `GET /download/ankrshield.apk` 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 /enterprise/audit-log
`apps/api/src/main.ts` declares `GET /enterprise/audit-log` 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 /enterprise/dpdp-report
`apps/api/src/main.ts` declares `GET /enterprise/dpdp-report` 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 /enterprise/pricing
`apps/api/src/main.ts` declares `GET /enterprise/pricing` 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 /integrations/email
`apps/api/src/main.ts` declares `GET /integrations/email` 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 /integrations/pagerduty
`apps/api/src/main.ts` declares `GET /integrations/pagerduty` 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 /integrations/telegram
`apps/api/src/main.ts` declares `GET /integrations/telegram` 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 /monitor/stats
`apps/api/src/main.ts` declares `GET /monitor/stats` 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 /proof
`apps/xshieldai-hanumang/src/routes/forja.ts` declares `GET /proof` 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 /risk/narrative
`apps/api/src/main.ts` declares `GET /risk/narrative` 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 /security/status
`apps/api/src/main.ts` declares `GET /security/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: GET /session/list
`apps/api/src/main.ts` declares `GET /session/list` 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 /state
`apps/xshieldai-hanumang/src/routes/forja.ts` declares `GET /state` 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 /taxii/
`apps/api/src/taxii/server.ts` declares `GET /taxii/` 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 /taxii/api/
`apps/api/src/taxii/server.ts` declares `GET /taxii/api/` 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 /taxii/api/collections/
`apps/api/src/taxii/server.ts` declares `GET /taxii/api/collections/` 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 /warrior/evidence-report
`apps/api/src/main.ts` declares `GET /warrior/evidence-report` 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 /warrior/honeypot-hits
`apps/api/src/main.ts` declares `GET /warrior/honeypot-hits` 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 /warrior/preblocked-ips
`apps/api/src/main.ts` declares `GET /warrior/preblocked-ips` 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 /warrior/threats/live
`apps/api/src/main.ts` declares `GET /warrior/threats/live` 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 /watch/domains
`apps/api/src/main.ts` declares `GET /watch/domains` 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 /api/feature-request
`apps/api/src/main.ts` declares `POST /api/feature-request` 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 /billing/webhook
`apps/api/src/main.ts` declares `POST /billing/webhook` 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 /device/push
`apps/api/src/main.ts` declares `POST /device/push` 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 /device/stats
`apps/api/src/main.ts` declares `POST /device/stats` 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 /enterprise/siem/test
`apps/api/src/main.ts` declares `POST /enterprise/siem/test` 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 /enterprise/siem/webhook
`apps/api/src/main.ts` declares `POST /enterprise/siem/webhook` 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 /warrior/android-check
`apps/api/src/main.ts` declares `POST /warrior/android-check` 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 /warrior/spyware-scan
`apps/api/src/main.ts` declares `POST /warrior/spyware-scan` 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/main.ts (5636 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/999219d0-f81f-4678-81ef-e9a326a84df2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/999219d0-f81f-4678-81ef-e9a326a84df2/

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.