api-mocking — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited api-mocking (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.
MSW handler API, browser/node setup, install commands and request-interception internals are canonical at vendor docs and drift on each release:
Need to mock HTTP for tests/dev?
├── Browser AND Node from one handler set → MSW
├── Node-only unit tests, low ceremony → nock
├── Need a stateful REST fake server (CRUD) → json-server
└── Browser-only with relational fixtures (factories) → Mirage JStypes/api.ts). A mock that compiles against stale types is the #1 source of mock-prod divergence.resetHandlers() (MSW) or cleanAll() (nock) in afterEach — leaked state across tests is a debugging tax.onUnhandledRequest: 'error' (MSW) so a typo'd URL fails loudly instead of silently passing.dev-tdd — mocks live in test setup; this skill activates from TDD workqa-e2e — Playwright/Cypress tests often layer MSW for deterministic stubsdev-testing-setup — wires the global setupServer into vitest/jest config~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.