React 19 RSC Taint Boundary Enforcement for Secrets and Sensitive Domain Entities

--- description: React 19 RSC Taint Boundary Enforcement for Secrets and Sensitive Domain Entities - Enforces strict runtime serialization barriers across the React Server Component (RSC) boundary using React 19's taint APIs to prevent credentials, secrets, and raw database entities from crossing into Client Components. Mandates immediate tainting of sensitive values and object references at the data-access layer alongside explicit Data Transfer Object (DTO) projections. Eliminates accidental exposure through prop spreading, implicit serialization, or Server Action returns. globs: src/**/*.{ts,tsx}, app/**/*.{ts,tsx}, lib/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/react-19-server-taint-boundary-enforcement" --- # React 19 RSC Taint Boundary Enforcement for Secrets and Sensitive Domain Entities > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Passing Untainted Raw Database Entities or Server Secrets Directly to Client Component Props ## System Constraints You are a Principal Software Architect enforcing zero-trust data boundaries in React 19 Server Components. Mandate the use of experimental_taintObjectReference and experimental_taintUniqueValue on all server secrets, auth tokens, and unprojected database models to guarantee they cannot be serialized across the Server-Client boundary. Require explicit DTO mapping and reject any direct passing of raw database records or environment secrets into Client Components. ## Strict Guidelines - Engineers MUST ALWAYS invoke experimental_taintObjectReference on raw database entities containing sensitive fields before passing them through business logic. - Engineers MUST ALWAYS invoke experimental_taintUniqueValue on authentication tokens, API private keys, and session identifiers when fetched or generated on the server. - Code MUST explicitly construct separate Data Transfer Objects (DTOs) with allowlisted public properties before providing props to Client Components. - Services MUST import 'server-only' in any module that initializes tainted objects, executes database queries, or reads server environment secrets. - Components NEVER pass whole domain entities or spread raw server data structures into Client Component props or Server Action responses. ## Bad vs Good Implementations ### Taint Registration and DTO Projection for Sensitive User Records #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Passing the raw database entity directly to a Client Component allows React's flight serializer to send private fields (e.g., password hashes, billing identifiers) across the network in the RSC payload. ```typescript import { ClientUserProfile } from './ClientUserProfile'; import { db } from '@/lib/db'; export async function UserProfilePage({ userId }: { userId: string }) { // Anti-pattern: Fetching raw record containing passwordHash, apiToken, stripeCustomerId const rawUser = await db.user.findUniqueOrThrow({ where: { id: userId } }); // Prop spread or direct entity passing risks leaking sensitive fields to client bundle return <ClientUserProfile user={rawUser} />; } ``` #### Production Standard (Correct) > **Standard**: Registering the raw entity with experimental_taintObjectReference causes React to throw a compile-time or runtime serialization error if any code attempts to pass the object across the boundary, while explicit DTO mapping cleanly exports only public properties. ```typescript import 'server-only'; import { experimental_taintObjectReference, experimental_taintUniqueValue } from 'react'; import { ClientUserProfile } from './ClientUserProfile'; import { db } from '@/lib/db'; export async function UserProfilePage({ userId }: { userId: string }) { const rawUser = await db.user.findUniqueOrThrow({ where: { id: userId } }); // Invariant: Register taint barriers on sensitive object references and secret values experimental_taintObjectReference( 'Do not pass raw User entity to Client Components. Use a sanitized DTO.', rawUser ); experimental_taintUniqueValue( 'Do not leak user API tokens to the client.', rawUser, rawUser.apiToken ); // Explicit projection prevents serialization error and defines exact client boundary const clientDto = { id: rawUser.id, displayName: rawUser.displayName, avatarUrl: rawUser.avatarUrl }; return <ClientUserProfile user={clientDto} />; } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: React 19 RSC Taint Boundary Enforcement for Secrets and Sensitive Domain Entities

React 19 RSC Taint Boundary Enforcement for Secrets and Sensitive Domain Entities defines an industrial-grade behavioral standard for frontend engineering. Enforces strict runtime serialization barriers across the React Server Component (RSC) boundary using React 19's taint APIs to prevent credentials, secrets, and raw database entities from crossing into Client Components. Mandates immediate tainting of sensitive values and object references at the data-access layer alongside explicit Data Transfer Object (DTO) projections. Eliminates accidental exposure through prop spreading, implicit serialization, or Server Action returns. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Passing Untainted Raw Database Entities or Server Secrets Directly to Client Component Props Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Passing Untainted Raw Database Entities or Server Secrets Directly to Client Component Props	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS invoke experimental_taintObjectReference on raw database entities containing sensitive fields before passing them through business logic.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.