kanbn/kan
7 issues need attention.
7 warnings in the paths between 11 routes and 2 tables.
- ROUTES
- 11
- TABLES
- 2
- FILES READ
- 120
- RULES RUN
- 7/7
7 findings
GET /api/mcp has no validator or rate limiter attached.
public-entry-guardedGET /api/oss-friends has no validator or rate limiter attached.
public-entry-guardedGET /api/v1/[...trpc] has no validator or rate limiter attached.
public-entry-guardedGET /api/v1/openapi.json has no validator or rate limiter attached.
public-entry-guardedOPTIONS /api/trpc/[trpc] has no validator or rate limiter attached.
public-entry-guardeduser_board_favorites is not connected to anything.
no-orphan-datastoreworkspace_slugs is not connected to anything.
no-orphan-datastore
Part of this repository was not read, so this report is incomplete. Read 120 of 420 files, schemas and routes first. Point Wyro at a single service directory to read one in full. Unread: apps/web/src/pages/api/partner/_utils.ts.
Free account, no card. The repository opens as an editable graph.
Add this check to the README
[](https://wyro.in/scan/kanbn/kan)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.