Architecture check
tropicoo/yt-dlp-bot
0 errors, 8 warnings
No critical or high-risk findings. 1 worth a look.
8 warnings in the paths between 8 routes and 1 tables.
Every file was read, but 3 places in them could not be parsed — listed under the findings.
Tables
1
Rules run
19/19
Findings by route
7 of 8 routes flagged · 19/19 rules ran
- Errors
- Warnings
- No findings
8 findings
1 medium7 low
8 findings, each with the route, the table it reaches, the file and line, and the fix. Free with an account.
3 places could not be parsed, so any route or table declared there is missing from this report:
yt_shared/src/yt_shared/models/task.py— class Task looks like a model but declares no __tablename__yt_shared/src/yt_shared/models/task.py— class File looks like a model but declares no __tablename__app_api/api/apps/healthcheck/routers/healthcheck.py— raw SQL — tables not resolved
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.