Architecture check

ManiMozaffar/linkedIn-scraper

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

0 errors, 16 warnings

No critical or high-risk findings. 2 worth a look.

16 warnings in the paths between 26 routes and 3 tables.

Findings

16

0 errors16 warningsDetails

Routes

26

13 with findingsGraph

Tables

3

Data models read

Rules run

19/19

75/75 source files read

Findings by route

13 of 26 routes flagged · 19/19 rules ran

  • Errors
  • Warnings
  • No findings
Each column is one route, in the order it is declaredRoute names unlock with a free account

16 findings

2 medium14 low

16 findings, each with the route, the table it reaches, the file and line, and the fix. Free with an account.

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.