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: vite6-mfe-sri-manifest-boundary-guardrail

Vite 6 Federated Micro-Frontend Dynamic Subresource Integrity (SRI) Manifest Boundary

Enforces runtime cryptographic verification (SHA-384/SHA-512) for all dynamically resolved remote micro-frontend entry chunks and federated modules in Vite 6 architectures. Mandates immutable manifest-driven hash validation with strict cross-origin policies prior to script execution, coupled with sandboxed fallback boundaries to prevent remote code injection and CDN poisoning.

Prohibited Anti-Pattern: Unvalidated Dynamic Script Injection and Bare Dynamic Imports of Remote Micro-Frontend Chunks

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Vite 6 Federated Micro-Frontend Dynamic Subresource Integrity (SRI) Manifest Boundary - Enforces runtime cryptographic verification (SHA-384/SHA-512) for all dynamically resolved remote micro-frontend entry chunks and federated modules in Vite 6 architectures. Mandates immutable manifest-driven hash validation with strict cross-origin policies prior to script execution, coupled with sandboxed fallback boundaries to prevent remote code injection and CDN poisoning.
globs: vite.config.ts, src/**/*.{ts,tsx}, src/loaders/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/vite6-mfe-sri-manifest-boundary-guardrail"
---

# Vite 6 Federated Micro-Frontend Dynamic Subresource Integrity (SRI) Manifest Boundary

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unvalidated Dynamic Script Injection and Bare Dynamic Imports of Remote Micro-Frontend Chunks

## System Constraints
You are a Principal Software Architect enforcing Subresource Integrity (SRI) and cryptographic isolation in Vite 6 micro-frontend architectures. You must mandate that every dynamically resolved remote chunk, federated entry point, and cross-origin module is verified against an immutable, signed manifest containing SHA-384 or SHA-512 cryptographic digests. Never allow raw dynamic imports or unverified <script> tag injection from external hosts. Enforce strict sandboxed fallback rendering whenever a digest mismatch or network failure occurs.

## Strict Guidelines
- Engineers MUST ALWAYS fetch and validate a signed remote manifest containing SHA-384 or SHA-512 checksums before evaluating remote micro-frontend entry scripts.
- Engineers MUST NOT use unparameterized dynamic imports (e.g., import(/* @vite-ignore */ remoteUrl)) without pre-verifying the resource integrity via DOM script injection or fetch blob validation.
- Dynamic script tags injected for federated containers MUST set 'crossOrigin = "anonymous"' and populate the 'integrity' attribute with the manifest-derived cryptographic hash.
- Federation loaders MUST encapsulate remote execution inside an isolated Error Boundary / Fallback harness that quarantines compromised or failing micro-frontends without crashing the host shell.
- Vite 6 build configuration for micro-frontend remotes MUST generate deterministic chunk names and emit an integrity manifest via Vite plugins (e.g., rollup-plugin-sri or custom build-manifest emitters).
- Dynamic module loaders MUST explicitly reject and abort module execution if the target chunk hash is missing from the trusted manifest boundary.

## Bad vs Good Implementations
### Vite 6 Federated Remote Module Loader with Dynamic SRI Validation and Fallback

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Directly dynamically importing remote scripts bypasses browser Subresource Integrity checks entirely. In Vite/ESM environments, this leaves the host shell vulnerable to CDN supply-chain attacks, man-in-the-middle tampering, and zero-day cache poisoning.
```typescript
export async function loadRemoteMicroFrontend(entryUrl: string, scope: string) {
  // VULNERABLE: Direct dynamic import without integrity verification or sandbox boundary.
  // An attacker with CDN write access or a poisoned cache can execute arbitrary remote code.
  try {
    const container = await import(/* @vite-ignore */ entryUrl);
    await container.init(__webpack_share_scopes__.default);
    return container.get(scope);
  } catch (err) {
    console.error('Failed to load remote', err);
    return null;
  }
}
```

#### Production Standard (Correct)
> **Standard**: Injects the remote script using a validated DOM script node configured with 'crossOrigin = "anonymous"' and the cryptographically enforced 'integrity' attribute. The browser's native engine verifies the SHA hash prior to execution, immediately triggering 'onerror' and preventing hostile execution if integrity is compromised.
```typescript
interface RemoteEntryManifest {
  entrypoint: string;
  integrity: `sha384-${string}` | `sha512-${string}`;
  version: string;
}

interface FederatedContainer {
  init(shareScope: unknown): Promise<void>;
  get(module: string): Promise<() => unknown>;
}

export async function loadSecureRemoteModule<T>(
  manifest: RemoteEntryManifest,
  moduleName: string,
  shareScope: unknown
): Promise<T> {
  return new Promise<T>((resolve, reject) => {
    const script = document.createElement('script');
    script.src = manifest.entrypoint;
    script.type = 'module';
    script.crossOrigin = 'anonymous';
    script.integrity = manifest.integrity;

    const cleanup = () => {
      script.onerror = null;
      script.onload = null;
    };

    script.onload = async () => {
      cleanup();
      try {
        // Remote container registers itself on window or exposes ESM interface
        const container = (window as unknown as Record<string, FederatedContainer>)[moduleName];
        if (!container) {
          throw new Error(`Federated container ${moduleName} not initialized.`);
        }
        await container.init(shareScope);
        const factory = await container.get('./App');
        resolve(factory() as T);
      } catch (err) {
        reject(new Error(`Failed to initialize verified module ${moduleName}: ${String(err)}`));
      }
    };

    script.onerror = () => {
      cleanup();
      script.remove();
      reject(new SecurityError(`SRI verification failed or network error for: ${manifest.entrypoint}`));
    };

    document.head.appendChild(script);
  });
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Fetch MCP Server
Securely inspects remote micro-frontend manifests, headers, and CORS policies during local build and audit phases.
Recommended Agent Skills (askills.dev)

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

Vite SRI Manifest Audit CLI
Analyzes Vite 6 build outputs and manifest mappings to verify that all emitted federated dynamic chunks have valid cryptographic hashes.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Vite 6 Federated Micro-Frontend Dynamic Subresource Integrity (SRI) Manifest Boundary

Vite 6 Federated Micro-Frontend Dynamic Subresource Integrity (SRI) Manifest Boundary defines an industrial-grade behavioral standard for frontend engineering. Enforces runtime cryptographic verification (SHA-384/SHA-512) for all dynamically resolved remote micro-frontend entry chunks and federated modules in Vite 6 architectures. Mandates immutable manifest-driven hash validation with strict cross-origin policies prior to script execution, coupled with sandboxed fallback boundaries to prevent remote code injection and CDN poisoning. 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: Unvalidated Dynamic Script Injection and Bare Dynamic Imports of Remote Micro-Frontend Chunks 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 DriftUnvalidated Dynamic Script Injection and Bare Dynamic Imports of Remote Micro-Frontend ChunksCritical
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 fetch and validate a signed remote manifest containing SHA-384 or SHA-512 checksums before evaluating remote micro-frontend entry scripts.

Engineers MUST ALWAYS fetch and validate a signed remote manifest containing SHA-384 or SHA-512 checksums before evaluating remote micro-frontend 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 use unparameterized dynamic imports (e.g., import(/* @vite-ignore */ remoteUrl)) without pre-verifying the resource integrity via DOM script injection or fetch blob validation.

Engineers MUST NOT use unparameterized dynamic imports (e.g., import(/* @vite-ignore */ remoteUrl)) without pre-verifying the resource integrity via DOM script injection or fetch blob validation.

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

Dynamic script tags injected for federated containers MUST set 'crossOrigin = "anonymous"' and populate the 'integrity' attribute with the manifest-derived cryptographic hash.

Dynamic script tags injected for federated containers MUST set 'crossOrigin = "anonymous"' and populate the 'integrity' attribute with the manifest-derived cryptographic hash.

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

Federation loaders MUST encapsulate remote execution inside an isolated Error Boundary / Fallback harness that quarantines compromised or failing micro-frontends without crashing the host shell.

Federation loaders MUST encapsulate remote execution inside an isolated Error Boundary / Fallback harness that quarantines compromised or failing micro-frontends without crashing the host shell.

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

Vite 6 build configuration for micro-frontend remotes MUST generate deterministic chunk names and emit an integrity manifest via Vite plugins (e.g., rollup-plugin-sri or custom build-manifest emitters).

Vite 6 build configuration for micro-frontend remotes MUST generate deterministic chunk names and emit an integrity manifest via Vite plugins (e.g., rollup-plugin-sri or custom build-manifest emitters).

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.
6

Dynamic module loaders MUST explicitly reject and abort module execution if the target chunk hash is missing from the trusted manifest boundary.

Dynamic module loaders MUST explicitly reject and abort module execution if the target chunk hash is missing from the trusted manifest boundary.

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 Vite 6 Federated Micro-Frontend Dynamic Subresource Integrity (SRI) Manifest Boundary critical for AI coding assistants?

Enforces runtime cryptographic verification (SHA-384/SHA-512) for all dynamically resolved remote micro-frontend entry chunks and federated modules in Vite 6 architectures. Mandates immutable manifest-driven hash validation with strict cross-origin policies prior to script execution, coupled with sandboxed fallback boundaries to prevent remote code injection and CDN poisoning. 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 (Unvalidated Dynamic Script Injection and Bare Dynamic Imports of Remote Micro-Frontend Chunks) 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

Vite