- handbook
- Company
- Company
- Board
- Communications
- Decision making
- Guides
- KPIs and OKRs
- principles
- Remote Work
- Security
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Third-Party Risk Management Policy
- Human Resources Security Policy
- Access Control Policy
- Incident Response Plan
- Cryptography Policy
- Information Security Policy and Acceptable Use Policy
- Secure Development Policy
- Data Management Policy
- strategy
- values
- Operations
- Product
- Feedback
- Market Segments
- Metrics
- Node-RED Dashboard
- personas
- Pricing Principles
- Principles
- Responsibilities
- Strategy
- Versioning
- Customer department
- Customer
- Customer Success
- Hubspot
- Marketing
- How we work
- Marketing
- Video
- Customer Stories
- Social Media
- blog
- Community
- Marketing - Website
- FlowFuse Messaging
- Webinars
- Sales
- Engineering & Design Practices
- Design
- Engineering
- Certified Nodes
- contributing
- Front End
- Packaging Guidelines
- Platform Ops
- Deployment
- Incident Response
- Observability
- Production Environment
- FlowFuse Dedicated
- Staging Environment
- Project Management
- Releases
- Security Policy
- tools
- Website A/B Testing
- Internal Operations
- People Ops
FlowFuse maintains a catalogue of nodes from the community that we put through regular checks to ensure they are of high quality and standards for use by our customers.
The catalogue is maintained in the certified-nr-nodes(🔒) repository.
A daily GH action runs the audit process across all nodes and regenerates the catalogue.json file served to Node-RED instances within FlowFuse.
# Proposing a new node to be included
- Raise an issue(🔒) with details of the node to be added.
- Assign the issue to the CTO (or in his absence, another member of the Engineering Team).
# Adding a new node to the list
Full details on the technical process are provided in the certified-nr-nodes(🔒) readme.
- Perform due diligence on the module; how popular is it, is it well maintained, is there a backlog of open issues etc.
- Add the module to the list held in
modules.json - Run the audit locally to check the current state of the module. Review the results and assess whether we can accept it into the catalogue in its current state.
- Raise a PR with the updated module list and audit output for the module.
- Review the PR with the CTO/Engineering Team