Everything in the atlas
Type
Domain
Origin
Signals
More: 8
Group by: Capability
Groups npm audit findings by root dependency, with failing thresholds
It audits through npm: a project that resolves its dependencies with another package manager, or has no `package.json`, has nothing for it to run. What it reports is what `npm audit` knows, so a vulnerability outside the npm advisory data is not in its table.
UI5 build task warning when the app's UI5 version reaches EOCP
The version list comes from ui5.sap.com, so a build that cannot reach it has nothing to match the project's version against. It checks the version written in `ui5.yaml`; a framework version a deployed app loads from elsewhere is outside what it sees.
Yeoman generator for Application Frontend config in UI5 libraries
It targets the Application Frontend service only — not the HTML5 application repository — fixes authentication to IAS, and always creates new service instances, so reusing existing ones means editing the generated `mta.yaml` afterwards. Version 0.1.0 is the only release.
UI5 server middleware proxying route prefixes to a backend
Release and repository quiet for 36 months.
UI5 Tooling v4 extension that registers other extensions
UI5 builder task preparing build output for the cachebuster
Release and repository quiet for 66 months.
UI5 build task warning when the app's UI5 version reaches EOCP
The version list comes from ui5.sap.com, so a build that cannot reach it has nothing to match the project's version against. It checks the version written in `ui5.yaml`; a framework version a deployed app loads from elsewhere is outside what it sees.
UI5 builder task transpiling ES6 to ES5 with Babel
Release and repository quiet for 50 months.
Groups npm audit findings by root dependency, with failing thresholds
It audits through npm: a project that resolves its dependencies with another package manager, or has no `package.json`, has nothing for it to run. What it reports is what `npm audit` knows, so a vulnerability outside the npm advisory data is not in its table.
Static check that each exported TypeScript function has a test
It reads TypeScript exports only; a project written in plain JavaScript has no exported functions for it to extract. A call to the function name in a test file counts as tested, and a call through property access such as `.foo(` does not.
Jest environment running UI5 unit tests in Node.js
Command line running UI5 QUnit and OPA tests in parallel
Vitest environment running UI5 unit tests in Node.js
WebdriverIO service running QUnit test pages
CLI translating UI5 i18n.properties files with OpenAI
