Architecture check

SAP-samples/fiori-elements-v4-cap-advanced

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

0 errors, 20 warnings

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

20 warnings in the paths between 17 routes and 15 tables.

Every file was read, but 5 places in them could not be parsed — listed under the findings.

Findings

20

0 errors20 warningsDetails

Routes

17

8 with findingsGraph

Tables

15

Data models read

Rules run

19/19

29/29 source files read

Findings by route

8 of 17 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

20 findings

7 medium13 low

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

5 places could not be parsed, so any route or table declared there is missing from this report:

  • srv/travel-service.cds — function getBookingDataOfPassenger — handler body is JavaScript, tables not resolved from CDS
  • srv/travel-service.cds — action createTravelByTemplate — handler body is JavaScript, tables not resolved from CDS
  • srv/travel-service.cds — action rejectTravel — handler body is JavaScript, tables not resolved from CDS
  • srv/travel-service.cds — action acceptTravel — handler body is JavaScript, tables not resolved from CDS
  • srv/travel-service.cds — action deductDiscount — handler body is JavaScript, tables not resolved from CDS

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.