Files
HealthLog/eslint-plugins/healthlog/__tests__/safe-fetch-required.test.mjs
T
Marc-André Bombeck 6633f0fb19 fix(lint): cover the unguarded egress paths and aliased fetch
Two spellings the egress guard could not see, both probed.

src/proxy.ts, src/instrumentation.ts and src/cli/ sat outside the enforced
roots (src/lib/ and src/app/), and the companion api-fetch-required guards
the client surface, so it did not reach them either. A raw fetch dropped
into instrumentation.ts linted clean. All three are egress-free today, but
instrumentation is exactly where an exporter pointed at an operator-supplied
URL would land.

The callee match knew the identifier `fetch` and the globalThis / window /
self member forms only, so an aliased import escaped it in every file:
`import { fetch as f } from "undici"` then `f(url)` linted clean under
src/lib. That spelling is what src/lib/safe-fetch.ts itself writes. Local
names bound to an imported `fetch`, and namespace-imported `ns.fetch(…)`,
are now callees; the wrapper internals and test files stay exempt as
before, and the wrapper's own aliased import is pinned as a valid case.

Adds the rule's missing unit-test file. The header records what the
binding scan still cannot see: require(), dynamic import, a fetch passed
as a parameter, and egress that never spells fetch at all.
2026-09-03 01:50:25 +02:00

146 lines
4.7 KiB
JavaScript

import { describe, it } from "vitest";
import { RuleTester } from "eslint";
import rule from "../safe-fetch-required.js";
RuleTester.describe = describe;
RuleTester.it = it;
RuleTester.itOnly = it.only;
const ruleTester = new RuleTester({
languageOptions: {
ecmaVersion: 2023,
sourceType: "module",
parserOptions: { ecmaFeatures: { jsx: true } },
},
});
ruleTester.run("safe-fetch-required", rule, {
valid: [
{
code: "safeFetch(url, { requirePublicHost: true });",
filename: "/repo/src/lib/notifications/senders/ntfy.ts",
},
// Same-origin relative paths never leave the origin.
{
code: 'fetch("/api/measurements");',
filename: "/repo/src/app/dashboard/load.ts",
},
{
code: "fetch(`/api/measurements/${id}`);",
filename: "/repo/src/lib/queries/measurements.ts",
},
// The wrapper's own internals, including the aliased undici import it
// actually uses. This is the spelling the rule learned to see, so the
// exemption has to be proven, not assumed.
{
code: 'import { fetch as undiciFetch } from "undici"; undiciFetch(url);',
filename: "/repo/src/lib/safe-fetch.ts",
},
{
code: "fetch(url);",
filename: "/repo/src/lib/safe-fetch-dispatcher.ts",
},
{
code: "fetch(url);",
filename: "/repo/src/lib/api/api-fetch.ts",
},
// Tests mock and assert against fetch directly.
{
code: 'import { fetch as f } from "undici"; f(url);',
filename: "/repo/src/lib/__tests__/egress.test.ts",
},
{
code: "fetch(url);",
filename: "/repo/src/lib/__mocks__/transport.ts",
},
// Outside every enforced path: scripts and config are out of scope.
{
code: "fetch(url);",
filename: "/repo/scripts/backfill.ts",
},
// An aliased import pointed at a relative path is still same-origin.
{
code: 'import { fetch as f } from "undici"; f("/api/version");',
filename: "/repo/src/lib/version.ts",
},
// A named import that is not `fetch` binds nothing this rule cares about.
{
code: 'import { Agent } from "undici"; Agent(url);',
filename: "/repo/src/lib/safe-fetch-dispatcher-helper.ts",
},
],
invalid: [
{
code: "fetch(url);",
filename: "/repo/src/lib/ai/openai-client.ts",
errors: [{ messageId: "rawFetch" }],
},
{
code: "globalThis.fetch(url);",
filename: "/repo/src/app/api/withings/route.ts",
errors: [{ messageId: "rawFetch" }],
},
{
code: "self.fetch(url);",
filename: "/repo/src/lib/pwa/register.ts",
errors: [{ messageId: "rawFetch" }],
},
{
code: 'globalThis["fetch"](url);',
filename: "/repo/src/lib/ai/local-client.ts",
errors: [{ messageId: "rawFetch" }],
},
// Protocol-relative and backslash forms resolve off-origin, so the
// same-origin exemption must not swallow them.
{
code: 'fetch("//evil.example/api");',
filename: "/repo/src/lib/ai/anthropic-client.ts",
errors: [{ messageId: "rawFetch" }],
},
// The three paths that sat outside the enforced roots. They are
// egress-free today; instrumentation.ts is where an exporter pointed at
// an operator-supplied URL would land, and nothing would have said so.
{
code: "fetch(url);",
filename: "/repo/src/proxy.ts",
errors: [{ messageId: "rawFetch" }],
},
{
code: "fetch(otlpEndpoint, { method: 'POST' });",
filename: "/repo/src/instrumentation.ts",
errors: [{ messageId: "rawFetch" }],
},
{
code: "fetch(url);",
filename: "/repo/src/cli/mcp-stdio.ts",
errors: [{ messageId: "rawFetch" }],
},
// The aliased import. `src/lib/safe-fetch.ts` writes exactly this
// spelling, so it is a form the codebase demonstrably reaches for, and
// the identifier check never matched it.
{
code: 'import { fetch as f } from "undici"; f(url);',
filename: "/repo/src/lib/ai/codex-client.ts",
errors: [{ messageId: "rawFetch" }],
},
{
code: 'import { fetch as undiciFetch } from "undici"; undiciFetch(url);',
filename: "/repo/src/instrumentation.ts",
errors: [{ messageId: "rawFetch" }],
},
// The namespace form of the same escape.
{
code: 'import * as undici from "undici"; undici.fetch(url);',
filename: "/repo/src/lib/notifications/senders/telegram.ts",
errors: [{ messageId: "rawFetch" }],
},
// A default import named `fetch` was always caught; kept so the widening
// cannot regress it.
{
code: 'import fetch from "node-fetch"; fetch(url);',
filename: "/repo/src/lib/ai/local-client.ts",
errors: [{ messageId: "rawFetch" }],
},
],
});