a public repository, read by nittim
Is n8n-io/n8n production ready?
What nittim read in this repository, and what it found. Public repository, public reading — sourced from its own code and dependency manifests, nothing else.
Workflow automation with hundreds of third-party integrations.
TypeScript · 201.5k stars
No verdict. The rule-based check reports hard evidence, or reports that it found none. Neither is a judgment on whether this code is safe to ship.
What was read — rule-based scan
Rule-based checks run on nittim's servers — a secret scanner and a dependency check, no model in the path. The code reached those two and stopped there.
Read 500 of 27113 eligible files. Commit fca3170. 2026-08-21.
What the scanners found
- Committed secrets on production paths
- 1
- Vulnerable runtime dependencies
- 1
nodemailer (GHSA-p6gq-j5cr-w38f)
Run it yourself
Scan any public repository in seconds — no sign-in, no card. Audit it to have a model read the code. Loop the report into your assistant to get the fixes applied and re-checked.
Scan your own repoQuestions
- What did nittim read in n8n-io/n8n?
- nittim read 500 of 27113 eligible files in n8n-io/n8n. The reading ran on August 21, 2026. It was taken at commit fca3170.
- Did nittim find committed secrets or vulnerable dependencies in n8n-io/n8n?
- The rule-based scan found 1 committed secret and 1 vulnerable dependency in n8n-io/n8n. Affected: nodemailer (GHSA-p6gq-j5cr-w38f).
- Is n8n-io/n8n production ready?
- A free scan is not a verdict. A full audit gives one.
More like this
More TypeScript repositories →
Add the badge to your README
[](https://nittim.com/library/n8n-io/n8n)