msw-setup — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited msw-setup (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Project scaffolding for MSW + the MCP client bridge. For runtime handler changes after setup, use the msw-cli skill.
--framework vite).mocks/, env vars, entry point).connected: true (this only proves the WebSocket bridge, not that the first browser requests were intercepted).msw-cli status misses.Do not duplicate the full setup guide in chat — execute from msw-cli setup output.
npm install / npx msw init (as the guide describes).NEXT_PUBLIC_MSW_WS_URL (Next.js), VITE_MSW_WS_URL (Vite), or MSW_WS_URL (Rspack/Rsbuild/Webpack) — must match the port from msw-cli open. (MCP_SERVER_URL is accepted as a legacy fallback.)app/layout.tsx is a Server Component; the MSW bootstrap must be a `'use client'` gate so the app subtree does not mount (and fetch) before initMocks() finishes. Follow the guide’s gated MswProvider pattern — do not start MSW in a parallel useEffect while rendering the full tree./msw-setup in an MCP client; the same guide backs both paths.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.