prisma/blog-backend-rest-api-nestjs-prisma
8 issues need attention.
8 warnings in the paths between 7 routes and 1 tables.
- ROUTES
- 7
- TABLES
- 1
- FILES READ
- 15
- RULES RUN
- 7/7
8 findings
GET / has no validator or rate limiter attached.
public-entry-guardedPOST /articles has no validator or rate limiter attached.
public-entry-guardedGET /articles has no validator or rate limiter attached.
public-entry-guardedGET /articles/drafts has no validator or rate limiter attached.
public-entry-guardedGET /articles/:id has no validator or rate limiter attached.
public-entry-guardedPATCH /articles/:id has no validator or rate limiter attached.
public-entry-guardedDELETE /articles/:id has no validator or rate limiter attached.
public-entry-guardedArticle 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/prisma/blog-backend-rest-api-nestjs-prisma)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.