josephgoksu/prime-nestjs

0 errors, 6 warningsmain

6 issues need attention.

6 warnings in the paths between 11 routes and 2 tables.

ROUTE FINDINGS4 of 11 · 7/7 rules
ROUTES
11
TABLES
2
FILES READ
29
RULES RUN
7/7

6 findings

  • POST /auth/login has no validator or rate limiter attached.

    public-entry-guarded

  • POST /auth/register has no validator or rate limiter attached.

    public-entry-guarded

  • GET / has no validator or rate limiter attached.

    public-entry-guarded

  • GET /health-check has no validator or rate limiter attached.

    public-entry-guarded

  • user is not connected to anything.

    no-orphan-datastore

  • task is not connected to anything.

    no-orphan-datastore

Part of this repository was not read, so this report is incomplete. Unread: src/main.ts.

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/josephgoksu/prime-nestjs)](https://wyro.in/scan/josephgoksu/prime-nestjs)

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.