a public repository, read by nittim
Is discourse/discourse 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.
The Rails forum software running much of the web's community discussion.
Ruby · 47.7k 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 24408 eligible files. Commit 36698aa. 2026-08-21.
What the scanners found
- Committed secrets on production paths
- 0
- Vulnerable runtime dependencies
- 1
postcss (GHSA-r28c-9q8g-f849)
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 discourse/discourse?
- nittim read 500 of 24408 eligible files in discourse/discourse. The reading ran on August 21, 2026. It was taken at commit 36698aa.
- Did nittim find committed secrets or vulnerable dependencies in discourse/discourse?
- The rule-based scan found 0 committed secrets and 1 vulnerable dependency in discourse/discourse. Affected: postcss (GHSA-r28c-9q8g-f849).
- Is discourse/discourse production ready?
- A free scan is not a verdict. A full audit gives one.
More like this
Add the badge to your README
[](https://nittim.com/library/discourse/discourse)