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

sergeiudo/sudo-airs-demo-portal

https://github.com/sergeiudo/sudo-airs-demo-portal · scanned 2026-06-16 00:07 UTC (2 months, 2 weeks ago)

91 raw signals (0 security + 91 graph)

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

Complete repo analysis

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

JSON
Combined
59.4
/100
Security checks
59
0 findings
System graph
59
100.0% cov · 91 findings
Critical
1
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 1 High 19 Medium 20 Low 30 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 91 Crowd 0 Layer: Software 1 Frontend 19 Network 1 Security 14 Cicd 1 Quality 22 Api 33
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 59.4/100 with 100.0% coverage. It contains 626 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 91 findings — concentrated in api (33), quality (22), frontend (19). Risk profile is high: 1 critical, 19 high, 20 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 70 of 91 actionable findings. 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 src/views/DeveloperCornerView.jsx
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
src/views/DeveloperCornerView.jsx:470
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/gateway/configs (src/views/llm-gateway/components/PortkeyStatusStrip.jsx:16)
`src/views/llm-gateway/components/PortkeyStatusStrip.jsx:16` calls `GET /api/gateway/configs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/gateway/configs` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/gateway/configs (src/views/llm-gateway/LiveDemoTab.jsx:118)
`src/views/llm-gateway/LiveDemoTab.jsx:118` calls `GET /api/gateway/configs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/gateway/configs` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/gateway/health (src/views/llm-gateway/components/PortkeyStatusStrip.jsx:15)
`src/views/llm-gateway/components/PortkeyStatusStrip.jsx:15` calls `GET /api/gateway/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/gateway/health` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/gateway/health (src/views/LlmGatewayView.jsx:19)
`src/views/LlmGatewayView.jsx:19` calls `GET /api/gateway/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/gateway/health` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/gateway/models (src/views/llm-gateway/components/ModelPicker.jsx:13)
`src/views/llm-gateway/components/ModelPicker.jsx:13` calls `GET /api/gateway/models` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/gateway/models` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/models/${provider} (src/components/api-intercept/ModelSelector.jsx:67)
`src/components/api-intercept/ModelSelector.jsx:67` calls `GET /api/models/${provider}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/models/<p>` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://ip-api.com/json/${ip}?fields=country,regionName,city,status (server.js:1406)
`server.js:1406` calls `GET http://ip-api.com/json/${ip}?fields=country,regionName,city,status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/ip-api.com/json/<p>` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/api/health (server.js:1491)
`server.js:1491` calls `GET http://localhost:${PORT}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/health` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${scannerPort}/ (server.js:746)
`server.js:746` calls `GET http://localhost:${scannerPort}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/gateway/chat (src/hooks/usePortkeyChat.js:35)
`src/hooks/usePortkeyChat.js:35` calls `POST /api/gateway/chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/gateway/chat` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/gateway/compare (src/views/llm-gateway/LiveDemoTab.jsx:67)
`src/views/llm-gateway/LiveDemoTab.jsx:67` calls `POST /api/gateway/compare` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/gateway/compare` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.portkey.ai/v1/chat/completions (portkey-routes.js:139)
`portkey-routes.js:139` calls `POST https://api.portkey.ai/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.portkey.ai/v1/chat/completions` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth.apps.paloaltonetworks.com/oauth2/access_token (server.js:642)
`server.js:642` calls `POST https://auth.apps.paloaltonetworks.com/oauth2/access_token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth.apps.paloaltonetworks.com/oauth2/access_token` If this points at an …
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `execute_code` without auth dependency — mcp-server/mcp_server.py:139
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
mcp-server/mcp_server.py:139 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `get_memory` without auth dependency — mcp-server/mcp_server.py:173
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
mcp-server/mcp_server.py:173 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `read_file` without auth dependency — mcp-server/mcp_server.py:72
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
mcp-server/mcp_server.py:72 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `scan_model` without auth dependency — scanner_app.py:1296
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
scanner_app.py:1296 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `set_memory` without auth dependency — mcp-server/mcp_server.py:184
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
mcp-server/mcp_server.py:184 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `web_fetch` without auth dependency — mcp-server/mcp_server.py:106
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
mcp-server/mcp_server.py:106 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — server.js: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 — src/hooks/useObservability.js:32
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 — src/views/DeveloperCornerView.jsx:231
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 — src/views/ModelScanningView.jsx:156
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 — src/views/ObservabilityView.jsx:334
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 — src/views/RedTeamingView.jsx:100
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 ci, tests. 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 'cors_wildcard' in mcp-server/mcp_server.py:38
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
mcp-server/mcp_server.py:38 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in scanner_app.py:218
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
scanner_app.py:218 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in scanner_server.py:49
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
scanner_server.py:49 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in server.js:23
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
server.js:23 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/AIRS-Claude-Code-Hooks-Guide.html:1767
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/AIRS-Claude-Code-Hooks-Guide.html:1767 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/hooks-guide.html:1779
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/hooks-guide.html:1779 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server.js:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
server.js:16 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scanner_app.py:159
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 40 placeholder/mock markers across 18 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 network Security conf 1.00 Privileged port 10 in use
Port 10 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
setup-slack-notify.sh Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 77 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — src/components/model-scanning/ScannerPanel.jsx:67
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph quality Integrity conf 1.00 15 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AWS_SESSION_TOKEN`, `AZURE_OPENAI_API_KEY`, `AZURE_OPENAI_API_VERSION`, `AZURE_OPENAI_DEPLOYMENT`, `AZURE_OPENAI_ENDPOINT`, `BEDROCK_REGION`, `CHATBOT_API_KEY`, `HF_SCAN_GROUP_UUID` + 7 more. Add them (with a placeholder/comment) to .env.example s…
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: ci, tests. 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 50 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 software Dead code conf 1.00 Possibly dead Python function: handler
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
aws-chatbot-target/handler.py:26
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 — server.js:268
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: GET /
`scanner_server.py` 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 /api/health
`server.js` declares `GET /api/health` 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/models/azure
`server.js` declares `GET /api/models/azure` 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/models/bedrock
`server.js` declares `GET /api/models/bedrock` 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/models/vertex
`server.js` declares `GET /api/models/vertex` 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/redteam/scan
`server.js` declares `GET /api/redteam/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 api Wiring conf 1.00 Unused endpoint: GET /api/redteam/targets/:id
`server.js` declares `GET /api/redteam/targets/: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 /api/release-notes
`server.js` declares `GET /api/release-notes` 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 /configs
`portkey-routes.js` declares `GET /configs` 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 /models
`portkey-routes.js` declares `GET /models` 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/chat
`server.js` declares `POST /api/chat` 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/cot
`server.js` declares `POST /api/cot` 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/redteam/proxy
`server.js` declares `POST /api/redteam/proxy` 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 /compare
`portkey-routes.js` declares `POST /compare` 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 /tools/execute_code
`mcp-server/mcp_server.py` declares `POST /tools/execute_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: POST /tools/get_memory
`mcp-server/mcp_server.py` declares `POST /tools/get_memory` 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 /tools/read_file
`mcp-server/mcp_server.py` declares `POST /tools/read_file` 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 /tools/set_memory
`mcp-server/mcp_server.py` declares `POST /tools/set_memory` 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 /tools/web_fetch
`mcp-server/mcp_server.py` declares `POST /tools/web_fetch` 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 /api/gateway
`server.js` declares `USE /api/gateway` 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: server.js (1522 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/components/api-intercept/TelemetrySidebar.jsx (1155 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/views/McpSecurityView.jsx (1675 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/57d96034-bbbb-403f-a3f7-7ee73ac2addc/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/57d96034-bbbb-403f-a3f7-7ee73ac2addc/

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.