Most API security incidents don't start with a clever zero-day. They start with something ordinary: a missing request-size limit, a trust proxy setting that lets anyone spoof their IP address, a logger that quietly writes passwords and tokens to disk, or a session cookie without the Secure flag. These are configuration problems, and they are easy to miss in a busy codebase.
At Satsai Infocom we're building Bug-Free Eureka, a free and open-source toolkit that helps Node.js and Express developers catch exactly these kinds of misconfigurations — early, automatically, and without changing how their app is deployed.
Why another security tool?
Many security tools ask you to adopt something new: a hosted scanner, a proxy in front of your API, a database, an account or a subscription. That's a real barrier for small teams and side projects.
Bug-Free Eureka takes the opposite approach. It is designed to run inside your existing application and workflow:
- No separate server. It never starts its own HTTP server or changes your port.
- No mandatory infrastructure. No database, Redis, Docker, cloud account or API key is required.
- No silent changes. It doesn't rewrite your routes, run migrations or change production behaviour without you opting in.
- Free and open source. Licensed under Apache-2.0 and developed in public on GitHub.
What it does
The project is organised into a small set of independent packages, so you only install what you need.
1. The auditor (@bug-free-eureka/core)
A deterministic rule engine that inspects your project's configuration and reports findings. Every finding has an ID, a default severity, evidence and a suggested fix. The planned first rules include:
| Rule | What it checks |
|---|---|
| BFE-001 | Missing recommended security headers |
| BFE-003 | Missing request-body size limit |
| BFE-005 | Sensitive data (passwords, tokens, OTPs) in configured logging |
| BFE-006 | Unsafe trusted-proxy configuration |
| BFE-002, 004, 007, 008 | CORS on sensitive endpoints, login rate limits, stack traces in production, insecure session cookies |
2. The CLI (@bug-free-eureka/cli)
Run an audit from your terminal or CI pipeline with init and audit commands, output as JSON or SARIF (so results can appear in GitHub code scanning), and a --fail-on option to fail a build at the severity you choose.
3. The Express adapter (@bug-free-eureka/express)
Optional, opt-in middleware: a request rate limiter (in-memory or Redis-compatible for multi-instance deployments), an audit logger that redacts secrets, and hardening helpers.
Principles we won't compromise on
Security tools have to be trustworthy themselves. These rules are written into the project from day one:
- Unknown is not a pass. If a rule can't establish the facts — for example, how your reverse proxy or CDN is configured — it reports
not_assessedinstead of pretending everything is fine. - Deterministic results. The same input always produces the same findings. No network calls, clocks or randomness inside rule logic.
- Never execute scanned code. The static audit only reads and parses files, with size and path-traversal limits.
- No secrets in output. Reports, logs, errors and test snapshots must never contain tokens, passwords, cookies or auth headers.
- Honest claims. We don't promise that your API is "secure" or "OWASP compliant". Bug-Free Eureka finds common, well-defined misconfigurations; it is not a replacement for a penetration test or a security review. Platform support is claimed only once CI proves it.
Built for real deployments
Node.js APIs run everywhere: EC2, Azure, Google Cloud, DigitalOcean, Docker, Kubernetes, PM2, behind Nginx or Apache, and behind load balancers. Many of the hardest bugs live at those boundaries — client IP detection, HTTPS termination, forwarded headers, and rate limits shared across instances. Bug-Free Eureka is designed with these setups in mind, and it targets Node.js 22, 24 and 26 on Linux, Windows and macOS.
Where the project is today
Bug-Free Eureka is in active early development and not yet published to npm.
- ✅ Repository foundation: TypeScript workspaces, builds that ship both ESM and CommonJS, linting, testing and release tooling
- ✅ The core security rule engine, including the
not_assessedresult and report builder - ✅ BFE-001 (security headers)
- 🔄 BFE-003 (request limits) and BFE-006 (trusted proxy) in review
- ⏳ Next: sensitive-logging rule and redaction, the CLI, the Express adapter, cross-platform CI, and documentation
Our current plan is a beta in January 2027 and a stable v1.0 in February 2027 — though, as our roadmap says, security beats schedule. We'll only ship when the release checks pass.
Get involved
Bug-Free Eureka is open source, and contributions are welcome — whether that's code, testing on your own deployment setup, proposing a new rule, or improving the docs.
- ⭐ Star the repo: github.com/bitsaspidy/bug-free-eureka
- 🐛 Report a bug or propose a rule using the issue templates on GitHub
- 🔒 Found a vulnerability? Please report it privately on GitHub instead of opening a public issue
- 💙 Support the project: GitHub Sponsors is coming soon
If your team builds APIs with Node.js and Express, we'd love your feedback. Follow along on GitHub, and stay tuned to the Satsai Infocom blog for updates as we approach the first release.
