Neutrx is maintained as an open-source project for secure Node.js backend service-to-service HTTP. This page explains where users should ask for help, where security reports belong, and how sponsorship supports ongoing maintenance.
Use GitHub issues for:
Open an issue at:
Before opening an issue, search existing issues and include the Neutrx version, Node.js version, operating system, expected behavior, actual behavior, and a minimal reproduction when practical. Redact tokens, cookies, credentials, customer data, internal hostnames, private URLs, and logs that may expose secrets.
Do not report suspected vulnerabilities in public issues, discussions, pull requests, or social posts.
Use the private vulnerability reporting process in the Security Policy:
Maintainers review public support requests on a best-effort basis. Sponsorship helps fund maintenance, security review, documentation, examples, compatibility work, and release validation, but it does not create a private support SLA, security embargo exception, roadmap guarantee, or priority queue unless a maintainer explicitly agrees to separate terms.
Security-sensitive fixes, regressions in supported Node.js versions, package integrity issues, and documentation that affects safe production usage may be prioritized ahead of general feature requests.
Users and organizations that depend on Neutrx can support development through GitHub Sponsors:
OpenCollective is not configured for this project at this time. If maintainers add an OpenCollective account later, update .github/FUNDING.yml, package.json, this support policy, and the README together so every support path stays consistent.