react-doctor/artifact-env-leak

A real secret shipped in a browser bundle under a public env prefix (`NEXT_PUBLIC_`, `VITE_`, `REACT_APP_`, `EXPO_PUBLIC_`) is world-readable and must be treated as compromised.

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Fires only in a browser-shipped artifact (generated/minified bundle, .map, or a file under public//dist/assets//.next/static//out//storybook-static/; documentation .md/.mdx is excluded). Two shapes: (1) a public-prefixed env name that names a secret: NEXT_PUBLIC_/VITE_/REACT_APP_/EXPO_PUBLIC_ followed by a token containing SECRET/TOKEN/PASSWORD/PRIVATE/DATABASE_URL/SERVICE_ROLE/AWS_ACCESS_KEY/AWS_SECRET (a server secret mistakenly given a client-published prefix); or (2) a full-env-dump shape: process.env/import.meta.env/window.__ENV__ co-occurring with a known server-secret name like DATABASE_URL/AWS_SECRET_ACCESS_KEY/SESSION_SECRET/COOKIE_SECRET/PRIVATE_KEY/SERVICE_ROLE.

Suppress when: already exempted: public-prefixed names that are genuinely client-safe (SENTRY_DSN, *PUBLISHABLE*, *ANON_KEY*, POSTHOG_TOKEN, CLERK_PUBLISHABLE_KEY, ALGOLIA_SEARCH_KEY, and NEXT_PUBLIC_ENABLE_*/DISABLE_*/ALLOW_*/REQUIRE_* feature flags) are skipped; a remaining FP is a secret-looking NAME that holds no real secret value (a documented placeholder).

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

• Confirmed failure: The required evidence establishes the violation.
• Rejected: A documented exception or false-positive predicate applies.
• Needs evidence: Named evidence can still be collected.
• Unavailable: Required evidence cannot be collected in this run.
• Waived with evidence: An authorized, scoped exception applies to an established failure.
• Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

A NEXT_PUBLIC_/VITE_/REACT_APP_/EXPO_PUBLIC_ prefix publishes the value to the browser, so never put a real secret behind one. Rename the variable to an unprefixed, server-only env var, read it only in server code (route handlers, server components, API routes), and rebuild so it leaves the client bundle. Rotate any key that already shipped. For full-env dumps, stop serializing process.env/import.meta.env into client config and allowlist only the public keys you mean to expose.

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.