Nodejs-agent
This app acts as a digital health monitor for your Node.js software.
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
71/100 Good
- Maintained
- 100last commit 1 day ago
- Popular
- 601,000 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
- Security check
- 73no serious findings, 3 minor, CI, tests, OpenSSF Scorecard 6.6/10
Based on 4 of 5 factors.
- GitHub stars
- 1,000
- Open issues
- 52
- Last commit
- 2026-11-20
- Latest release
- v14.13.0
- License
- Apache-2.0
- Activity
- rising
Checked yesterday - source: GitHub (newrelic/node-newrelic)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Create a .env file with your key Create a .env file in the app folder with NEVERBOUNCE_API_KEY=your_key. Without this small settings file, the included examples cannot authenticate and API calls will fail. source
- Use your real key, not the sample Replace the sample secret_x... value with the actual key from your NeverBounce account before running. The example key is only a placeholder and will not work. source
- Start only waiting jobs If you created a job with auto_start off, call jobs.start with its job ID when you're ready. Jobs must be waiting, or the start call won't begin verification. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Do I need a New Relic account before configuring the agent?
Yes, you should have a New Relic account before starting. Add your license key and application or service name to the agent configuration file.
How do I make sure the agent is loaded before my application code?
Run the program with node -r newrelic your-program.js, or require('newrelic') before any other module if you cannot change the start command.
How is Next.js instrumentation handled?
Use the hybrid agent functionality for Next.js. It includes loading the hybrid agent instrumentation and injecting the browser agent.
What configuration change is needed for ES Modules?
If you rely on a configuration file, rename it from newrelic.js to newrelic.cjs so it can be properly loaded. The configuration contents behave the same after the rename.
Can I use the agent in production without testing first?
No, you should test the agent before using it in production. It is an instrumentation tool, so verify it in your environment first.
Answers sourced from github.com
Community
- self-hosted pipeline agents: NVM installed but NPM/Node ... - Reddit (reddit)
- Is there a good self-hosted version of Heroku that'll let me ... - Reddit (reddit)
- Is Self-Hosting A Node.JS web app feasible? : r/selfhosted - Reddit (reddit)
Collected 48 days ago - public community threads