Skip to content

Security: abap2UI5/docs

Security

SECURITY.md

Security policy

Reporting a vulnerability

Please use the GitHub Security Advisory "Report a Vulnerability" tab. Do not open a public issue for a security report.

Expect an acknowledgement within a few days. This project is developed alongside other work, so a fix is agreed rather than promised by a date — the advisory is where that conversation happens.

Supported versions

Only what is currently published at abap2ui5.github.io/docs is supported. There are no released versions to patch: main is the site, and a fix is deployed by merging it.

What this site is, from a security point of view

  • There is no server. The site is static files built by VitePress and served from GitHub Pages. No backend, no SAP system, no account, no session, and nothing a reader types is sent anywhere.
  • The one thing that executes is the Run button. A fenced example that carries one links into abap2UI5/playground, which transpiles the ABAP and runs it in the reader's own browser. The code travels in the URL fragment, which a browser never sends to a server. The playground's own security policy covers what happens once the reader is there.
  • The pages are not a source of truth about the framework. The API reference, the version numbers and the sample links are generated from, or checked against, abap2UI5 and its sibling repositories at a pinned release. A wrong statement here is usually wrong there first — but report it here if that is where you found it.
  • Dependencies are pinned, and the generators fetch only from raw.githubusercontent.com at that pin.

Out of scope

  • A page that is out of date, incomplete, or wrong about the framework. That is a documentation bug and belongs in an issue — it is what the eight checks in AGENTS.md exist to catch, so a report that names one they missed is genuinely useful.
  • Anything a reader does to their own browser tab with code they wrote themselves.

There aren't any published security advisories