TomDoesTech/Testing-Express-REST-API
9 issues need attention.
9 warnings in the paths between 8 routes and 3 tables.
- ROUTES
- 8
- TABLES
- 3
- FILES READ
- 24
- RULES RUN
- 7/7
9 findings
POST /api/users has no validator or rate limiter attached.
public-entry-guardedPOST /api/sessions has no validator or rate limiter attached.
public-entry-guardedPOST /api/products has no validator or rate limiter attached.
public-entry-guardedPUT /api/products/:productId has no validator or rate limiter attached.
public-entry-guardedGET /api/products/:productId has no validator or rate limiter attached.
public-entry-guardedDELETE /api/products/:productId has no validator or rate limiter attached.
public-entry-guardedusers is not connected to anything.
no-orphan-datastoreproducts is not connected to anything.
no-orphan-datastoresessions is not connected to anything.
no-orphan-datastore
Free account, no card. The repository opens as an editable graph.
Add this check to the README
[](https://wyro.in/scan/TomDoesTech/Testing-Express-REST-API)It updates itself whenever the repository changes and links back to this report.
What this is
Wyro reads the repository’s routes and data models and checks the paths between them: whether a route can reach a table without passing a guard, whether a datastore holding personal data is exposed to a public read, whether an endpoint that issues credentials requires the credentials it issues.
It is rule-based, not a model. The same commit produces the same result every time, and it does not guess at business rules it cannot see. A rule with nothing to look at is reported as not having run — never as a pass.
This check runs on public source through GitHub’s own API and needs no account. A free account adds the editable architecture canvas, private repositories on paid plans, and a CI gate. No card required.