‹ Reports
The Dispatch

OSS Report: n8n-io/n8n


n8n Project Sees Active Development with Focus on Code Modernization and Bug Fixes

The n8n project, an open-source workflow automation tool, continues to evolve with active contributions aimed at enhancing functionality, modernizing the codebase, and improving user experience.

Recent Activity

Recent pull requests indicate a strong focus on refactoring components to use Vue's composition API, suggesting a concerted effort to modernize the codebase (e.g., PRs #10919, #10917, #10916). Bug fixes are also prominent, addressing issues like incorrect behavior in workflows (#10926) and UI inconsistencies (#10922). These activities reflect a trajectory towards improved maintainability and user interaction.

Development Team and Recent Contributions

  1. Raúl Gómez Morales (r00gm)

    • Refactored DuplicateWorkflowDialog.vue and SettingsSidebar.vue.
    • Fixed modal overflow in the Code Node.
  2. Elias Meire (elsmr)

    • Fixed modal overflow with AI in the Code Node.
    • Worked on editor UI bug fixes.
  3. Iván Ovejero (ivov)

    • Simplified subscriber handler setters.
    • Refactored execution post-execute promises.
  4. Mutasem Aldmour (mutdmour)

    • Fixed telemetry console errors.
    • Enhanced Assistant functionality.
  5. Ricardo Espinoza (RicardoE105)

    • Migrated components to the composition API.
    • Refactored editor UI components.
  6. Milorad Filipović (MiloradFilipovic)

    • Fixed AI Assistant chat styling issues.
    • Migrated components to the composition API.
  7. Tomi Turtiainen (tomi)

    • Prevented concurrent benchmark execution.
    • Upgraded Cypress for CI/CD improvements.
  8. Michael Kret (michael-radency)

    • Fixed HTTP Request Node issues.
    • Enhanced Google Calendar Node.
  9. Danny Martini (despairblue)

    • Implemented new partial execution logic for workflows.
  10. Csaba Tuncsik (cstuncsik)

    • Worked on UI fixes for source control modals.

Of Note

Quantified Reports

Quantify Issues



Recent GitHub Issues Activity

Timespan Opened Closed Comments Labeled Milestones
7 Days 13 9 33 0 1
30 Days 51 33 179 0 1
90 Days 132 92 476 29 1
1 Year 348 198 1426 145 1
All Time 1766 1559 - - -

Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.

Quantify commits



Quantified Commit Activity Over 30 Days

Developer Avatar Branches PRs Commits Files Changes
Tomi Turtiainen 5 31/29/1 53 760 104979
Ricardo Espinoza 5 18/17/0 26 531 31616
कारतोफ्फेलस्क्रिप्ट™ 5 29/27/1 39 635 16589
Iván Ovejero 10 25/19/2 52 999 13174
Elias Meire 6 12/8/0 17 59 9928
oleg 2 7/6/0 16 46 4331
Danny Martini 6 5/1/0 11 47 3763
Milorad FIlipović 3 9/8/0 13 59 3722
Alex Grozav 5 4/2/0 25 67 3319
Raúl Gómez Morales 5 15/12/0 29 50 2888
Shireen Missi 4 4/3/0 10 36 2503
Csaba Tuncsik 4 5/3/0 10 79 1780
Michael Kret 3 3/1/0 14 24 1104
Mutasem Aldmour 3 7/5/0 8 24 1071
Eugene 3 4/3/0 10 22 768
CodeShakingSheep 1 0/0/0 1 3 401
Cornelius Suermann 2 0/0/0 2 4 270
github-actions[bot] 2 9/9/0 4 17 260
Jon 4 4/1/0 5 6 225
aya (ayatnkw) 2 2/0/0 6 3 141
Ria Scholz 1 0/0/0 1 1 37
Val 1 0/0/0 1 3 28
Marc Littlemore 1 0/0/0 1 1 2
Manuel Voppmann 1 0/0/0 1 1 2
oscarpedrero 1 0/0/0 1 1 2
Stanimira Rikova (Stamsy) 0 1/0/0 0 0 0
Wesley Schell (wsdevv) 0 1/0/0 0 0 0
Jay Hartley (arose26) 0 1/0/0 0 0 0
Idan Fishman (idanfishman) 0 1/0/0 0 0 0
Taj Noah (AlAgawani) (tajalagawani) 0 1/0/1 0 0 0
None (feelgood-interface) 0 1/0/0 0 0 0
None (SebastjanPrachovskij) 0 1/0/1 0 0 0

PRs: created by that dev and opened/merged/closed-unmerged during the period

Detailed Reports

Report On: Fetch issues



Recent Activity Analysis

The n8n project has seen a significant uptick in recent GitHub issue activity, with 207 open issues currently. Notably, several issues have been created or updated within the last week, indicating ongoing development and user engagement. A common theme among these issues is the presence of bugs related to specific integrations and nodes, particularly concerning error handling and data processing.

Several issues reveal critical problems, such as the inability of certain nodes to handle specific data formats or conditions correctly. For instance, the Kafka trigger (#10933) fails to listen for messages, while the Todoist node (#10914) incorrectly returns success without validating server responses. These recurring problems suggest potential weaknesses in the integration logic across various nodes.

Additionally, there are indications of inconsistencies in how workflows handle errors and manage state, as seen in issues related to Redis and MongoDB nodes. The presence of multiple unresolved bugs may impact user experience and could hinder adoption if not addressed promptly.

Issue Details

Most Recently Created Issues

  1. Issue #10933: Kafka trigger don't listen but emits an error

    • Priority: High
    • Status: Open
    • Created: 0 days ago
    • Updated: N/A
  2. Issue #10914: Todoist node always returns Success without checking server response

    • Priority: High
    • Status: Open
    • Created: 2 days ago
    • Updated: N/A
  3. Issue #10913: docker-entrypoint.sh startup script has incorrect export statement

    • Priority: Medium
    • Status: Open
    • Created: 3 days ago
    • Updated: N/A
  4. Issue #10911: [Text Classifier] Problem in node ‘Text Classifier‘ Could not get parameter - System Prompt Template

    • Priority: Medium
    • Status: Open
    • Created: 3 days ago
    • Updated: N/A
  5. Issue #10901: Langchain nodes not respecting HTTP proxy settings

    • Priority: Medium
    • Status: Open
    • Created: 3 days ago
    • Updated: N/A

Most Recently Updated Issues

  1. Issue #10892: Webhook node doesn't accept binary data

    • Priority: High
    • Status: Open
    • Created: 4 days ago
    • Updated: 4 days ago
  2. Issue #10836: Outdated duplicate workflow

    • Priority: Low
    • Status: Open
    • Created: 7 days ago
    • Updated: 5 days ago
  3. Issue #10834: Notion Database Page Update Node | Can't set properties

    • Priority: Medium
    • Status: Open
    • Created: 7 days ago
    • Updated: 6 days ago
  4. Issue #10833: Deactivated Trigger with pinned data is always used

    • Priority: Medium
    • Status: Open
    • Created: 7 days ago
    • Updated: 6 days ago
  5. Issue #10831: Valid Notion page IDs are rejected

    • Priority: Medium
    • Status: Open
    • Created: 7 days ago
    • Updated: 1 day ago

Summary of Implications

The recent activity indicates that while n8n is actively maintained, there are critical bugs that need addressing to improve user experience and functionality. The presence of multiple issues related to core integrations suggests that developers should prioritize testing and validation processes for these components to ensure reliability.

The recurring themes of error handling and data processing across various nodes highlight potential areas for improvement in the overall architecture of the n8n platform. Addressing these issues may enhance stability and user satisfaction significantly.

Report On: Fetch pull requests



Overview

The analysis of the pull requests (PRs) for the n8n project reveals a diverse range of contributions, including bug fixes, feature enhancements, and refactoring efforts. The project shows active development with a focus on improving functionality, user experience, and code maintainability.

Summary of Pull Requests

  1. PR #10931: Fixes an issue by enabling the Assistant on other credential views, enhancing user interaction across different sections of the application.
  2. PR #10926: Addresses a bug where expressions in pagination code did not have access to execution data, which could lead to incorrect behavior in workflows.
  3. PR #10924: Prevents concurrent execution of benchmarks, ensuring accurate performance measurements without interference from other processes.
  4. PR #10923: Corrects an issue where the original request object was modified when sanitizing messages for the UI, potentially leading to unexpected behavior.
  5. PR #10922: Improves the editor's UI by preventing unnecessary expansion of node name inputs in the Node Design View (NDV), enhancing layout consistency.
  6. PR #10921: Updates button focus styles to use :focus-visible, improving accessibility and user experience by preventing unwanted focus styles during mouse interactions.
  7. PR #10919: Migrates TemplatesInfoCarousel.vue to the composition API, aligning with modern Vue practices and potentially improving performance and readability.
  8. PR #10917: Similar to PR #10919, this PR migrates TemplatesCollectionView.vue to the composition API, further standardizing the codebase.
  9. PR #10916: Continues the migration effort by converting SettingsLdapView.vue to the composition API, contributing to a more maintainable code structure.
  10. PR #10915: Cleans up unused components like PageAlert.vue, reducing clutter in the codebase and improving maintainability.

Analysis of Pull Requests

Themes and Commonalities

  • Refactoring and Modernization: A significant number of PRs focus on refactoring existing components to use Vue's composition API. This trend indicates an effort to modernize the codebase, making it more maintainable and aligned with current best practices in Vue development (e.g., PRs #10919, #10917, #10916).

  • Bug Fixes and Enhancements: Several PRs address specific bugs or enhance existing functionality (e.g., PRs #10931, #10926). These contributions are crucial for improving user experience and ensuring the reliability of the application.

  • UI/UX Improvements: PRs like #10922 and #10921 focus on subtle UI/UX improvements that enhance user interaction without altering core functionality. Such changes are important for maintaining a polished and user-friendly interface.

Notable Anomalies

  • The presence of multiple PRs related to the same theme (e.g., migration to composition API) suggests a coordinated effort or initiative within the development team to update and improve specific areas of the codebase systematically.

  • Some PRs (e.g., #10924) address operational aspects like CI/CD improvements or testing enhancements, highlighting ongoing efforts to improve development workflows alongside feature development.

Old PRs and Merge Activity

  • The analysis does not reveal any significantly old or stale PRs that lack recent merge activity. This suggests an active maintenance effort where contributions are regularly reviewed and integrated into the main branch.

Conclusion

The n8n project demonstrates a healthy development ecosystem with active contributions focused on enhancing functionality, modernizing the codebase, and improving user experience. The systematic approach to refactoring and bug fixing indicates a commitment to maintaining high-quality standards as the project evolves.

Report On: Fetch commits



Repo Commits Analysis

Development Team and Recent Activity

Team Members and Recent Contributions

  1. Raúl Gómez Morales (r00gm)

    • Recent Activity:
    • Refactored DuplicateWorkflowDialog.vue and SettingsSidebar.vue to script setup.
    • Fixed modal overflow in the Code Node.
    • Addressed clipboard XSS injection issues.
    • Collaborated with multiple team members on various components.
  2. Elias Meire (elsmr)

    • Recent Activity:
    • Fixed modal overflow when AI is enabled in the Code Node.
    • Contributed to fixing node name input expansion in NDV.
    • Worked on various bug fixes related to the editor UI.
  3. Iván Ovejero (ivov)

    • Recent Activity:
    • Simplified subscriber handler setters and refactored execution post-execute promises.
    • Contributed to multiple core refactoring tasks, including Redis pubsub class hierarchy and worker server setup.
    • Collaborated on telemetry events and metrics.
  4. Mutasem Aldmour (mutdmour)

    • Recent Activity:
    • Fixed telemetry issues causing console errors.
    • Enhanced Assistant functionality across various credential views.
  5. Ricardo Espinoza (RicardoE105)

    • Recent Activity:
    • Migrated several components to the composition API, including TemplatesCollectionView.vue.
    • Conducted extensive refactoring across the editor UI components.
  6. Milorad Filipović (MiloradFilipovic)

    • Recent Activity:
    • Fixed styling issues in AI Assistant chat and improved design system components.
    • Worked on migrating components to the composition API.
  7. Tomi Turtiainen (tomi)

    • Recent Activity:
    • Prevented benchmarks from running concurrently and upgraded Cypress.
    • Contributed significantly to CI/CD improvements.
  8. Michael Kret (michael-radency)

    • Recent Activity:
    • Fixed issues in HTTP Request Node and contributed to Google Calendar Node enhancements.
  9. Danny Martini (despairblue)

    • Recent Activity:
    • Implemented new partial execution logic for acyclic workflows.
  10. Csaba Tuncsik (cstuncsik)

    • Recent Activity:
    • Worked on various UI fixes, including source control modals.

Patterns and Themes

  • The team is actively refactoring components to use the composition API, indicating a shift towards modern practices in Vue.js development.
  • There is a strong focus on fixing bugs related to user interface elements, particularly around the AI Assistant and editor functionalities.
  • Collaboration among team members is evident, with many commits co-authored or involving multiple contributors on related tasks.
  • Continuous integration improvements are being made, particularly regarding testing frameworks and CI/CD workflows.

Conclusions

The development team is engaged in a robust cycle of feature enhancement, bug fixing, and modernization of the codebase through refactoring efforts. The collaborative nature of their work suggests a cohesive team dynamic focused on improving both functionality and user experience within the n8n platform.