React 19 RSC Taint API & Cryptographic Boundary Enforcement

--- description: React 19 RSC Taint API & Cryptographic Boundary Enforcement - Enforces strict cryptographic serialization boundaries in React 19 Server Components using experimental_taintUniqueValue and taintObjectReference. Guarantees that internal database records, private API tokens, and cryptographic keys are blocked at the RSC serialization layer from leaking to client bundles. globs: src/**/*.{ts,tsx}, app/**/*.{ts,tsx}, lib/**/*.{ts,tsx}, server/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/react-19-rsc-taint-boundary-enforcement" --- # React 19 RSC Taint API & Cryptographic Boundary Enforcement > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Unchecked Secret and Session Deserialization Across RSC-to-Client Component Props ## System Constraints You are a Principal Software Architect enforcing React 19 RSC boundary security. Your mandate is to prevent accidental serialization and data exfiltration across React Server Component boundaries by enforcing experimental_taintUniqueValue and taintObjectReference at the Data Access Layer (DAL). ## Strict Guidelines - Engineers MUST ALWAYS invoke experimental_taintObjectReference on raw database entities containing sensitive fields before returning them from Data Access Layer (DAL) functions. - Engineers MUST ALWAYS invoke experimental_taintUniqueValue on specific sensitive string/binary scalar values, such as cryptographic salts, JWT secrets, payment tokens, and password hashes. - Code MUST import 'server-only' at the top of any module executing taint registration or managing secret credentials. - Services MUST project tainted domain entities into explicit, minimal Data Transfer Objects (DTOs) before passing data as props to Client Components marked with 'use client'. - Engineers MUST NOT disable React compiler taint warnings or bypass taint errors using shallow spreads or Object.assign to duplicate tainted object graphs. - Components NEVER pass un-sanitized server context, environment variables, or database transaction objects directly into Client Component tree props. ## Bad vs Good Implementations ### Leaking Untainted Database Entities Across RSC Boundaries #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: The raw user entity returned from the database contains sensitive fields (tokens, hashes, private IDs). Without taint enforcement, passing the object directly to a Client Component silently serializes the sensitive fields into the client's payload stream. ```typescript // lib/dal/user.ts import { db } from '@/lib/db'; export async function getUserAccount(userId: string) { // Anti-pattern: Raw entity containing private tokens is returned un-tainted const user = await db.users.findUnique({ where: { id: userId } }); return user; } // app/dashboard/page.tsx (Server Component) import { getUserAccount } from '@/lib/dal/user'; import { UserAvatarClient } from './UserAvatarClient'; export default async function Page({ params }: { params: { id: string } }) { const user = await getUserAccount(params.id); // VULNERABILITY: If UserAvatarClient is 'use client', user.stripeCustomerId, // passwordHash, and internal tokens are serialized to client RSC flight payloads. return <UserAvatarClient user={user} />; } ``` #### Production Standard (Correct) > **Standard**: Using experimental_taintObjectReference blocks accidental transmission of the full database row, while experimental_taintUniqueValue safeguards critical scalar secrets from leaking even if assigned to new objects. The DAL strictly returns a decoupled SafeUserDTO. ```typescript // lib/dal/user.ts import 'server-only'; import { experimental_taintObjectReference, experimental_taintUniqueValue } from 'react'; import { db } from '@/lib/db'; export interface SafeUserDTO { id: string; displayName: string; avatarUrl: string | null; } export async function getUserAccount(userId: string): Promise<SafeUserDTO> { const user = await db.users.findUniqueOrThrow({ where: { id: userId } }); // Invariant 1: Taint entire entity reference from RSC client serialization experimental_taintObjectReference( 'Do not pass raw user records to client components. Project to SafeUserDTO.', user ); // Invariant 2: Taint individual high-entropy sensitive scalars if (user.apiSecret) { experimental_taintUniqueValue( 'Do not leak API credentials to the client.', user, user.apiSecret ); } // Return an explicit, un-tainted public DTO projection return { id: user.id, displayName: user.displayName, avatarUrl: user.avatarUrl, }; } // app/dashboard/page.tsx (Server Component) import { getUserAccount } from '@/lib/dal/user'; import { UserAvatarClient } from './UserAvatarClient'; export default async function Page({ params }: { params: { id: string } }) { const userDto = await getUserAccount(params.id); return <UserAvatarClient user={userDto} />; } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: React 19 RSC Taint API & Cryptographic Boundary Enforcement

React 19 RSC Taint API & Cryptographic Boundary Enforcement defines an industrial-grade behavioral standard for frontend engineering. Enforces strict cryptographic serialization boundaries in React 19 Server Components using experimental_taintUniqueValue and taintObjectReference. Guarantees that internal database records, private API tokens, and cryptographic keys are blocked at the RSC serialization layer from leaking to client bundles. 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: Unchecked Secret and Session Deserialization Across RSC-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	Unchecked Secret and Session Deserialization Across RSC-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 returning them from Data Access Layer (DAL) functions.

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.