Architecture check

haixiangyan/nest-todo

masterRule-based: the same commit always gets the same result

Watch this repo Open in dashboard

All rules passed

This backend looks good.

No route reaches sensitive data without passing a guard, across 17 routes and 2 tables.

Findings

0 errors0 warnings

Routes

0 with findingsGraph

Tables

Data models read

Rules run

19/19

84/84 source files read

Findings by route

0 of 17 routes flagged · 19/19 rules ran

Errors
Warnings
No findings

Route 1 of 17No findings

Route 2 of 17No findings

Route 3 of 17No findings

Route 4 of 17No findings

Route 5 of 17No findings

Route 6 of 17No findings

Route 7 of 17No findings

Route 8 of 17No findings

Route 9 of 17No findings

Route 10 of 17No findings

Route 11 of 17No findings

Route 12 of 17No findings

Route 13 of 17No findings

Route 14 of 17No findings

Route 15 of 17No findings

Route 16 of 17No findings

Route 17 of 17No findings

Each column is one route, in the order it is declaredRoute names unlock with a free account

Nothing to report

Every rule that had something to look at ran, and none of them fired.

Open the architecture as a graph Watch for new findings

Watch this repo

An email when a push adds a new finding: the route, the file and the line. Free. No CI to install, nothing added to the repository.

Watch this repo

Check every pull request

Opens GitHub with the workflow already written. Commit it and each pull request gets this check, with the verdict as one comment. Findings already on master never fail one; only what a pull request adds can.

Add to nest-todo on GitHub

Add this check to the README

[![wyro architecture](https://wyro.in/api/badge/haixiangyan/nest-todo)](https://wyro.in/scan/haixiangyan/nest-todo)

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 findings, the editable architecture canvas, private repositories on paid plans, and a CI gate. No card required.

Maintain this repository? You can have this report removed, and a real vulnerability is disclosed to you privately before it is published. How public reports are handled.

Create a free account Check repos in your browser