Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
Reliability breakdown
Component scores measured daily from GitHub activity (2026-05-15).
Activity on 24 of 41 tracked days in the last 90 and 0 of 11 in the last 30.
Merged 932 of 1,222 PRs opened and closed 315 of 341 issues opened over the last 90 tracked days — PR flow carries 55% of this component, issue flow 45%.
0 releases in the last 180 days, 0 in the last 90 and 0 in the last 30 — a steady cadence scores highest.
Last push 0 days ago — freshness decays as pushes age (roughly halves every 83 days without a push).
344 open issues against 197,133 stars — about 2 open issues per 1,000 stars. Lighter backlogs score higher.
Modeled — lower is better; concentration of commits in few maintainers. Contributors graph
Measured history
Weekly GitHub totals with 30, 90, and 180 day views.
May 10, 2026
Current0
Previous0
Weekly star gains
GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.
131 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
May 10, 2026
Current124
Previous84
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
114 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
May 10, 2026
Current101
Previous103
Weekly total
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
114 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
May 10, 2026
Current408
Previous314
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
114 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
May 10, 2026
Current524
Previous300
Weekly total
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
114 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
May 10, 2026
Current301
Previous237
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
114 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
May 15, 2026
Current1.17
Previous2.67
Daily ratio — a gap means nothing was opened that day
How this works: each day's value is issues closed that day ÷ issues opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more issues than arrived that day.
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
114 observed daily rows. Missing days are not fabricated.
Per-day formula: issues closed that day ÷ issues opened that day; blank when nothing was opened (a gap, not a zero).
| Date | Issues opened | Issues closed | Stored score |
|---|
May 15, 2026
Current1.05
Previous0.64
Daily ratio — a gap means nothing was opened that day
How this works: each day's value is pull requests closed that day ÷ pull requests opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more pull requests than arrived that day.
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
114 observed daily rows. Missing days are not fabricated.
Per-day formula: pull requests closed that day ÷ pull requests opened that day; blank when nothing was opened (a gap, not a zero).
| Date | PRs opened | PRs closed | Stored score |
|---|
Join the conversation
Share what you know about n8n — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Explain what worked, what broke down, and what another team should know before adopting n8n.
Project Q&A
Browse implementation threads tied directly to n8n-io/n8n. Each question links through to the full answer page.
Be the first to ask how teams run n8n in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses n8n — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post