apollo-router
Audited by Runlayer on Feb 22, 2026
Malicious tool definition detected
Tool: SKILL.md [1/2] Description: --- name: apollo-router description: > Version-aware guide for configuring and running Apollo Router for federated GraphQL supergraphs. Generates correct YAML for both Router v1.x and v2.x.
Tool: SKILL.md [2/2] Description: with the generated config.
Malicious tool definition detected
Tool: divergence-map.md Description: # Apollo Router v1 ↔ v2 Config Divergence Map This document tracks every configuration section where v1 and v2 schemas differ in ways that break parsing or change behavior.
Malicious tool definition detected
Tool: references/configuration.md Description: # Router Configuration Reference The Router is configured via a YAML file (`router.yaml`).
Malicious tool definition detected
Tool: references/connectors.md Description: # Router Connectors Configuration (v2) Apollo Connectors are configured in Router v2 under the `connectors` key.
Malicious tool definition detected
Tool: references/headers.md Description: # Header Configuration Configure how the Router handles HTTP headers for requests to subgraphs and responses to clients.
Malicious tool definition detected
Tool: references/plugins.md Description: # Router Customization Extend Apollo Router functionality with Rhai scripts or external coprocessors.
Malicious tool definition detected
Tool: references/telemetry.md Description: # Router Telemetry Configure logging, metrics, and tracing with OpenTelemetry-compatible exporters.
Malicious tool definition detected
Tool: references/troubleshooting.md Description: # Router Troubleshooting Common issues and solutions when running Apollo Router.
Malicious tool definition detected
Tool: templates/v1/development.yaml Description: # ═══════════════════════════════════════════════════════════════ # Apollo Router Core — Development Configuration (v1.x) # NOTE: Use `router --dev` to auto-enable introspection + sandbox.
Malicious tool definition detected
Tool: templates/v1/production.yaml Description: # ═══════════════════════════════════════════════════════════════ # Apollo Router Core — Production Configuration (v1.x) # Generated for Router v1.17+ (operation limits GA) # NOTE: v1.x has reached end-of-support.
Malicious tool definition detected
Tool: templates/v1/sections/auth.yaml Description: # JWT Authentication — v1 (issuer is a singular string) authentication: router: jwt:
Malicious tool definition detected
Tool: templates/v1/sections/cors.yaml Description: # CORS — v1 flat schema cors: origins: - https://app.example.com - https://studio.apollographql.com allow_headers:
Malicious tool definition detected
Tool: templates/v1/sections/headers.yaml Description: # Header Propagation (v1 and v2 — identical schema) headers:
Malicious tool definition detected
Tool: templates/v1/sections/limits.yaml Description: # Operation Limits (v1.17+ and v2 — identical schema) # Tip: Start with warn_only: true to observe real traffic, then enforce.
Malicious tool definition detected
Tool: templates/v1/sections/telemetry.yaml Description: # Telemetry — v1 # v1 uses FTV1 reporting by default to GraphOS Studio.
Malicious tool definition detected
Tool: templates/v1/sections/traffic-shaping.yaml Description: # Traffic Shaping (v1 and v2 — identical schema) # NOTE: global_rate_limit under `router:` limits CLIENT requests.
Malicious tool definition detected
Tool: templates/v2/development.yaml Description: # ═══════════════════════════════════════════════════════════════ # Apollo GraphOS Router — Development Configuration (v2.x) # NOTE: Use `router --dev` to auto-enable introspection + sandbox.
Malicious tool definition detected
Tool: templates/v2/production.yaml Description: # ═══════════════════════════════════════════════════════════════ # Apollo GraphOS Router — Production Configuration (v2.x) # Generated for Router v2.10+ / Federation v2.12+ # ═══════════════════════════════════════════════════════════════ supergraph: listen: 0.0.0.0:4000 path: /graphql introspection: false query_planning: cache: in_memory: limit: 512 sandbox: enabled: false homepage: enabled: false health_check: enabled: true listen: 0.0.0.0:8088
Malicious tool definition detected
Tool: templates/v2/sections/auth.yaml Description: # JWT Authentication — v2 (issuers is plural, array) # BREAKING CHANGE from v1: `issuer` (string) → `issuers` (array).
Malicious tool definition detected
Tool: templates/v2/sections/connectors.yaml Description: # Connectors — v2 (GA) # Use `connectors` for current Router v2.
Malicious tool definition detected
Tool: templates/v2/sections/cors.yaml Description: # CORS — v2 policies schema # v2 uses a policies array instead of flat origins.
Malicious tool definition detected
Tool: templates/v2/sections/headers.yaml Description: # Header Propagation (v2 — identical schema to v1) headers:
Malicious tool definition detected
Tool: templates/v2/sections/limits.yaml Description: # Operation Limits (v2 — same schema as v1.17+) # Tip: Start with warn_only: true to observe real traffic, then enforce.
Malicious tool definition detected
Tool: templates/v2/sections/telemetry.yaml Description: # Telemetry — v2 # v2 uses OTLP-first reporting to GraphOS Studio (otlp_tracing_sampler defaults to 1.0).
Malicious tool definition detected
Tool: templates/v2/sections/traffic-shaping.yaml Description: # Traffic Shaping (v2 — identical schema to v1) # NOTE: global_rate_limit under `router:` limits CLIENT requests.
Malicious tool definition detected
Tool: validation/checklist.md Description: # Post-Generation Validation Checklist Run through this checklist after generating a `router.yaml` to catch common mistakes.