a public repository, read by nittim
Is payatu/Tiredful-API 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.
A REST API broken on purpose, for API-security practice.
Python · 583 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 84 of 130 eligible files. Commit 0134124. 2026-08-21.
What the scanners found
- Committed secrets on production paths
- 0
- Vulnerable runtime dependencies
- 2
Django (GHSA-337x-4q8g-prc5, GHSA-3gh2-xw74-jmcw)
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 payatu/Tiredful-API?
- nittim read 84 of 130 eligible files in payatu/Tiredful-API. The reading ran on August 21, 2026. It was taken at commit 0134124.
- Did nittim find committed secrets or vulnerable dependencies in payatu/Tiredful-API?
- The rule-based scan found 0 committed secrets and 2 vulnerable dependencies in payatu/Tiredful-API. Affected: Django (GHSA-337x-4q8g-prc5, GHSA-3gh2-xw74-jmcw).
- Is payatu/Tiredful-API 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/payatu/Tiredful-API)