DimiMikadze/fest

1 error, 8 warningsmain

9 issues need attention.

1 error and 8 warnings in the paths between 14 routes and 4 tables.

ROUTE FINDINGS5 of 14 · 7/7 rules
ROUTES
14
TABLES
4
FILES READ
93
RULES RUN
7/7

9 findings

  • GET /auth/delete-all can reach Organization without authenticating.

    auth-before-dataGET /auth/delete-all → Organization

  • GET /auth/delete-all reaches User without auth, which is expected for an authentication endpoint.

    auth-entry-publicGET /auth/delete-all → User

  • GET /auth/delete-all has no validator or rate limiter attached.

    public-entry-guarded

  • PATCH /organizations/update/:id has no validator or rate limiter attached.

    public-entry-guarded

  • PATCH /organizations/add-member has no validator or rate limiter attached.

    public-entry-guarded

  • DELETE /organizations/delete/:id has no validator or rate limiter attached.

    public-entry-guarded

  • POST /invitations/validate-token has no validator or rate limiter attached.

    public-entry-guarded

  • OrganizationUser is not connected to anything.

    no-orphan-datastore

  • Invitation is not connected to anything.

    no-orphan-datastore

Part of this repository was not read, so this report is incomplete. Unread: apps/api/src/main.ts, apps/api/src/users/users.controller.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/DimiMikadze/fest)](https://wyro.in/scan/DimiMikadze/fest)

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.