Nitro
Nitro is a Helm chart that helps operators deploy and manage Arbitrum Nitro, the execution environment used by the Arbitrum Ethereum Layer 2.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- 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.
55/100 Fair
- Maintained
- 94last commit 85 days ago
- Popular
- 60970 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 08 serious findings, 8 minor, CI, tests, OpenSSF Scorecard 4.7/10
Based on 4 of 5 factors.
Security check: 8 serious findings
- A GitHub workflow can be triggered by outsiders to run their code with the project's secrets (.github/workflows)
- Uses golang.org/x/crypto v0.48.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.48.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.48.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.48.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.48.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.48.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.48.0, which has a known critical vulnerability (Go)
Automated checks on commit ccc5c82, 28 Oct 2026. Not an audit.
Availability: platform listings confirmed today
- GitHub stars
- 970
- Open issues
- 80
- Last commit
- 2026-08-28
- Latest release
- v3.12.2
- Activity
- stale
Checked 14 days ago - source: GitHub (offchainlabs/nitro)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Point serverDir at your server code In nitro.config.ts, set serverDir (the folder Nitro treats as your server code) to the folder where your routes live, such as ./ for the example project. If it points to the wrong folder, Nitro may not find the routes or handlers you want to run. source
- Set runtime settings before starting If your server reads runtime settings, fill in values such as apiKey in runtimeConfig (settings Nitro can read while the server is running) before you start it. If a required value is blank, the app may start but the feature that uses that setting will not work. source
- Build before running the Bun server If you are using Bun (a fast JavaScript runtime), build the project first with the Bun preset (the build mode for Bun) and then start it with bun run ./.output/server/index.mjs. If you skip the build step, the generated server file will not exist, so the app cannot start. source
Fetched 41 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Community
Collected 48 days ago - public community threads