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

EvanBacon/serve-sim

https://github.com/EvanBacon/serve-sim · scanned 2026-05-16 22:30 UTC (18 hours, 53 minutes ago) · 10 languages

74 findings (9 legacy + 65 scanner) 65th percentile · Typescript · medium (20-100K LoC) Scanner says 89 (lower by 13)

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

Complete repo analysis

Last scanned 18 hours, 52 minutes ago · v1 · 74 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
86.3
/100
Repobility
83
9 legacy
9-layer
89
88.9% cov · 65 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 10 Medium 18 Low 31 Source: Legacy 9 9-layer 65 Crowd 0 Layer: Security 9 Quality 26 Software 19 Api 1 Frontend 15 Cicd 4

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Insecure pattern 'exec_used' in packages/serve-sim/dev.ts:458
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
packages/serve-sim/dev.ts:458
#2
Insecure pattern 'exec_used' in packages/serve-sim/src/client/location-emulation-tool.tsx:234
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
packages/serve-sim/src/client/location-emulation-tool.tsx:234
#3
Insecure pattern 'exec_used' in packages/serve-sim/src/client/utils/drop.ts:69
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
packages/serve-sim/src/client/utils/drop.ts:69
#4
Insecure pattern 'exec_used' in packages/serve-sim/src/client/utils/app-icon.ts:23
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
packages/serve-sim/src/client/utils/app-icon.ts:23
#5
Insecure pattern 'exec_used' in packages/serve-sim-client/src/transport.ts:364
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
packages/serve-sim-client/src/transport.ts:364
#6
Insecure pattern 'exec_used' in packages/serve-sim-client/src/gateway.ts:161
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
packages/serve-sim-client/src/gateway.ts:161
#7
Insecure pattern 'exec_used' in packages/serve-sim-client/src/simulator/useSimStream.ts:69
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
packages/serve-sim-client/src/simulator/useSimStream.ts:69
#8
No auth library detected
GapSeverity.MEDIUM Layer.SECURITY score 0.338
Why: medium severity
#9
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/publish.yml:65
#10
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/publish.yml

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}
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/445e6e2e-8b99-4dc2-ab93-4be9669a8976/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/445e6e2e-8b99-4dc2-ab93-4be9669a8976/

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.