Repo brief: n8n-io/n8n

Generated by RepoPilot · document generated 2026-09-17 · concise human review Evidence snapshot · analyzed 2026-09-17T03:33:23.819Z · commit 7821b9c5b722

Verdict

Mixed — Evidence incomplete — review before adopting

• Last commit today
• 48+ active contributors
• Distributed ownership (top contributor 7% of recent commits)
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

n8n is a fair-code workflow automation platform that combines a visual canvas editor with custom code support (JavaScript, Python) to build and deploy AI agents and multi-step workflows. It provides 1500+ native integrations, self-hosting capabilities, and enterprise-grade features like role-based access control and audit trails, enabling teams to automate business processes from prototype to production without vendor lock-in. Monorepo structure: packages/cli/ contains the core server and CLI infrastructure (abstract-server, commands registry, auth handlers), packages/ likely contains node implementations and integrations. Architecture separates concerns into services (auth, chat,…

Start here

Open these first:

• packages/cli/src/abstract-server.ts — Base server class that initializes the n8n platform, routing, middleware, and lifecycle management for all CLI commands.
• packages/cli/src/commands/start.ts — Primary entry point for starting the n8n server; orchestrates initialization of database, workflows, and API listeners.
• packages/cli/src/controllers/active-workflows.controller.ts — REST API controller managing workflow activation state and execution; core endpoint for workflow lifecycle.
• packages/cli/src/active-workflow-manager.ts — Manages in-memory registry and lifecycle of active workflows; bridges workflow definitions to runtime execution.
• packages/cli/src/auth/auth.service.ts — Centralized authentication service handling user credentials, JWT validation, and session management.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone the repository: git clone https://github.com/n8n-io/n8n.git && cd n8n. No package.json or Makefile is visible in the file list provided, so verify the repository root for npm/yarn/pnpm manifests before running i…

Daily commands:

Setup commands cannot be reliably inferred—no package.json, Makefile, or setup script visible in provided file list. Required verification steps: (1) Check repository root for package.json, yarn.lock, or `pnpm-l…

…shortened for this brief.

Key cautions & unknowns

• Could not verify license from the available repository evidence
• Database dependency: packages/cli/src/commands/db/revert.ts and migration system indicate mandatory database (likely PostgreSQL or SQLite); local dev requires database setup and schema initialization. **Docker…
• License evidence is incomplete or ambiguous.
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.