lujakob/nestjs-realworld-example-app

0 errors, 6 warningsmaster

6 issues need attention.

6 warnings in the paths between 21 routes and 5 tables.

ROUTE FINDINGS1 of 21 · 7/7 rules
ROUTES
21
TABLES
5
FILES READ
35
RULES RUN
7/7

6 findings

  • GET / has no validator or rate limiter attached.

    public-entry-guarded

  • follows is not connected to anything.

    no-orphan-datastore

  • tag is not connected to anything.

    no-orphan-datastore

  • user is not connected to anything.

    no-orphan-datastore

  • article is not connected to anything.

    no-orphan-datastore

  • comment 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

wyro architecture badge
[![wyro architecture](https://wyro.in/api/badge/lujakob/nestjs-realworld-example-app)](https://wyro.in/scan/lujakob/nestjs-realworld-example-app)

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.