a public repository, read by nittim
Is plausible/analytics 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.
Privacy-first web analytics in Elixir and Phoenix.
Elixir · 28.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 2027 eligible files. Commit 9cc669b. 2026-08-21.
What the scanners found
- Committed secrets on production paths
- 0
- Vulnerable runtime dependencies
- 2
brace-expansion (GHSA-mh99-v99m-4gvg, GHSA-rgw5-rvv9-x895)
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 plausible/analytics?
- nittim read 500 of 2027 eligible files in plausible/analytics. The reading ran on August 21, 2026. It was taken at commit 9cc669b.
- Did nittim find committed secrets or vulnerable dependencies in plausible/analytics?
- The rule-based scan found 0 committed secrets and 2 vulnerable dependencies in plausible/analytics. Affected: brace-expansion (GHSA-mh99-v99m-4gvg, GHSA-rgw5-rvv9-x895).
- Is plausible/analytics production ready?
- A free scan is not a verdict. A full audit gives one.
Add the badge to your README
[](https://nittim.com/library/plausible/analytics)