AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
frontendcritical PriorityID: vite-rolldown-federation-sri-attestation

Subresource Integrity Attestation and Contract Validation for Federated Micro-Frontends

Enforces deterministic cryptographic digest verification and strict runtime schema contract validation on dynamic remote container manifests and emitted Rolldown ESM chunks. Prevents edge supply-chain injection attacks and poisoned dynamic imports by requiring immutable SHA-384/SHA-512 SRI attestation headers before hydrating cross-origin micro-frontend components. Guarantees fail-closed isolation if dynamic remote modules diverge from pre-attested cryptographic lockfiles.

Prohibited Anti-Pattern: Blind Cross-Origin Remote Container Execution Without Cryptographic Digest Pinning and Runtime Type Enforcement

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Subresource Integrity Attestation and Contract Validation for Federated Micro-Frontends - Enforces deterministic cryptographic digest verification and strict runtime schema contract validation on dynamic remote container manifests and emitted Rolldown ESM chunks. Prevents edge supply-chain injection attacks and poisoned dynamic imports by requiring immutable SHA-384/SHA-512 SRI attestation headers before hydrating cross-origin micro-frontend components. Guarantees fail-closed isolation if dynamic remote modules diverge from pre-attested cryptographic lockfiles.
globs: vite.config.{ts,js,mjs}, src/**/federation/**/*.{ts,tsx}, src/**/remotes/**/*.{ts,tsx}, src/plugins/**/*.{ts,js}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/vite-rolldown-federation-sri-attestation"
---

# Subresource Integrity Attestation and Contract Validation for Federated Micro-Frontends

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Blind Cross-Origin Remote Container Execution Without Cryptographic Digest Pinning and Runtime Type Enforcement

## System Constraints
You are a Principal Security Architect enforcing zero-trust module boundaries within Vite 6 and Rolldown federated runtimes. You must prohibit unverified cross-origin script evaluation, dynamic dynamic-imports of foreign manifests without cryptographic integrity digests (SRI SHA-384/SHA-512), and untyped dynamic federation remotes. Mandate fail-closed runtime fetching protocols, manifest signature verification, and immutable schema validation via runtime boundary types.

## Strict Guidelines
- Engineers MUST ALWAYS verify remote federation manifests against signed SRI digests (sha384 or sha512) prior to evaluating remote entry scripts.
- Engineers MUST NOT inject dynamic remote entry points via unvetted DOM manipulation (e.g., dynamic script tag insertion without an integrity attribute and crossOrigin="anonymous").
- Code MUST employ an immutable attested manifest store that fails closed, aborting remote federation loading if hash mismatches or network tampering occur.
- Federated remote contracts MUST validate the exported runtime interface using strict Zod or TypeBox schema validation before mounting components into host DOM trees.
- Build scripts MUST configure Rolldown's output pipeline to generate deterministic chunk names and output integrity hashes into a verifiable client-side lockfile.

## Bad vs Good Implementations
### Dynamic Remote Loading: Insecure Blind Injection vs. Attested SRI Fetch with Schema Verification

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fetches remote code directly over the network without checking cryptographic digests (SRI), allowing compromised CDNs or poisoned DNS caches to inject malicious code directly into the authenticated host application context.
```typescript
import { init, loadRemote } from '@module-federation/runtime';

// VULNERABLE: Direct resolution without SRI check or contract attestation
export async function mountRemoteAnalytics(containerId: string) {
  init({
    name: 'host_app',
    remotes: [
      {
        name: 'analytics_remote',
        entry: 'https://cdn.partner.io/analytics/remoteEntry.js'
      }
    ]
  });

  // Untrusted code is fetched and executed with zero cryptographic verification
  const remoteModule = await loadRemote<any>('analytics_remote/Tracker');
  if (remoteModule && remoteModule.mount) {
    remoteModule.mount(document.getElementById(containerId));
  }
}
```

#### Production Standard (Correct)
> **Standard**: Enforces runtime cryptographic digest validation (SHA-384) directly via subresource integrity checks on the network layer and enforces strict runtime contract schema validation on the imported exports via Zod before execution.
```typescript
import { z } from 'zod';

// Production Invariant: Verified cryptographic attestation manifest
const RemoteAttestationRecord = z.object({
  url: z.string().url(),
  integrity: z.string().regex(/^sha(?:384|512)-[A-Za-z0-9+/=]+$/)
});
type RemoteAttestationRecord = z.infer<typeof RemoteAttestationRecord>;

const RemoteExportContract = z.object({
  mount: z.function().args(z.instanceof(HTMLElement)).returns(z.void()),
  unmount: z.function().args(z.instanceof(HTMLElement)).returns(z.void())
});
type RemoteExportContract = z.infer<typeof RemoteExportContract>;

const REMOTE_LOCKFILE: Readonly<Record<string, RemoteAttestationRecord>> = Object.freeze({
  'analytics_remote/Tracker': {
    url: 'https://cdn.partner.io/analytics/v2.1.0/tracker-chunk.mjs',
    integrity: 'sha384-oqVuAfXRKap7fdgcCY5uykM6+R9GqQ8K/uxy9rx7HNQlGYl1kPzQho1wx4JwY8wC'
  }
});

export async function loadAttestedRemote(moduleKey: keyof typeof REMOTE_LOCKFILE): Promise<RemoteExportContract> {
  const attestation = RemoteAttestationRecord.parse(REMOTE_LOCKFILE[moduleKey]);
  const response = await fetch(attestation.url, {
    mode: 'cors',
    cache: 'no-store',
    integrity: attestation.integrity
  });

  if (!response.ok) {
    throw new SecurityError(`Attested remote fetch failed: ${response.statusText}`);
  }

  const scriptBlob = await response.blob();
  const objectUrl = URL.createObjectURL(new Blob([scriptBlob], { type: 'application/javascript' }));

  try {
    const rawModule: unknown = await import(/* @vite-ignore */ objectUrl);
    return RemoteExportContract.parse(rawModule);
  } finally {
    URL.revokeObjectURL(objectUrl);
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Model Context Protocol Fetch
Validates live CDN remote headers, CORS assertions, and remote digest checksum availability.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Subresource Integrity Digest Generator
Calculates deterministic SHA-384 and SHA-512 SRI base64 hashes for emitted ESM Rolldown build targets.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Subresource Integrity Attestation and Contract Validation for Federated Micro-Frontends

Subresource Integrity Attestation and Contract Validation for Federated Micro-Frontends defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic cryptographic digest verification and strict runtime schema contract validation on dynamic remote container manifests and emitted Rolldown ESM chunks. Prevents edge supply-chain injection attacks and poisoned dynamic imports by requiring immutable SHA-384/SHA-512 SRI attestation headers before hydrating cross-origin micro-frontend components. Guarantees fail-closed isolation if dynamic remote modules diverge from pre-attested cryptographic lockfiles. 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: Blind Cross-Origin Remote Container Execution Without Cryptographic Digest Pinning and Runtime Type Enforcement 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 ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftBlind Cross-Origin Remote Container Execution Without Cryptographic Digest Pinning and Runtime Type EnforcementCritical
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 InconsistencyAI 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:

1

Engineers MUST ALWAYS verify remote federation manifests against signed SRI digests (sha384 or sha512) prior to evaluating remote entry scripts.

Engineers MUST ALWAYS verify remote federation manifests against signed SRI digests (sha384 or sha512) prior to evaluating remote entry scripts.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT inject dynamic remote entry points via unvetted DOM manipulation (e.g., dynamic script tag insertion without an integrity attribute and crossOrigin="anonymous").

Engineers MUST NOT inject dynamic remote entry points via unvetted DOM manipulation (e.g., dynamic script tag insertion without an integrity attribute and crossOrigin="anonymous").

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Code MUST employ an immutable attested manifest store that fails closed, aborting remote federation loading if hash mismatches or network tampering occur.

Code MUST employ an immutable attested manifest store that fails closed, aborting remote federation loading if hash mismatches or network tampering occur.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Federated remote contracts MUST validate the exported runtime interface using strict Zod or TypeBox schema validation before mounting components into host DOM trees.

Federated remote contracts MUST validate the exported runtime interface using strict Zod or TypeBox schema validation before mounting components into host DOM trees.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Build scripts MUST configure Rolldown's output pipeline to generate deterministic chunk names and output integrity hashes into a verifiable client-side lockfile.

Build scripts MUST configure Rolldown's output pipeline to generate deterministic chunk names and output integrity hashes into a verifiable client-side lockfile.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Subresource Integrity Attestation and Contract Validation for Federated Micro-Frontends critical for AI coding assistants?

Enforces deterministic cryptographic digest verification and strict runtime schema contract validation on dynamic remote container manifests and emitted Rolldown ESM chunks. Prevents edge supply-chain injection attacks and poisoned dynamic imports by requiring immutable SHA-384/SHA-512 SRI attestation headers before hydrating cross-origin micro-frontend components. Guarantees fail-closed isolation if dynamic remote modules diverge from pre-attested cryptographic lockfiles. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Blind Cross-Origin Remote Container Execution Without Cryptographic Digest Pinning and Runtime Type Enforcement) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related FRONTEND Rules

View all rules →
frontend
119

SolidStart 1.0 Server Functions & Async Boundaries Production Standard

SolidStart 1.0 relies on the Vinxi bundler to split `server$` closures into independent HTTP POST RPC endpoints. Direct lexical closure over client signals within `server$` scopes or failure to demarcate async boundaries with `<Suspense>` causes silent serialization failures, client-bundle secret leaks, and SSR hydration mismatches. Enforcing strict parameter passing, runtime input validation, and Solid async primitives maintains security and fine-grained reactivity across network boundaries.

frontend
119

Astro 5 Actions & Content Layer Production Standard

Enforces strict type safety and architectural correctness for Astro 5 Server Actions and the zero-waterfall Content Layer API. Prevents runtime contract mismatches, hydration mismatches, and unhandled mutation exceptions across dynamic and prerendered boundaries. Failure to follow these patterns leads to silent data fetching waterfalls, build-time cache corruptions, and unhandled server action exceptions.

frontend
51

Nuxt 4 Nitro Server Engine & Shared Directory Production Standard

Nuxt 4 enforces strict boundary segregation between client UI in the app/ directory, backend endpoints in server/, and universal contracts in shared/. Violating cross-boundary isolation or maintaining module-scoped state in Nitro server handlers causes catastrophic cross-request data corruption and hydration mismatches under concurrent production traffic. Architects must enforce request-isolated H3 event contexts, universal serialization schemas, and strict path-alias boundaries.

1 Rule in Stack

Subresource