Kernseife BTP App
The BTP side of Project KernseifeProject KernseifeA custom ABAP Test Cockpit check that scores how custom code uses SAP objects against a classification the customer writes, as a measure of clean core technical debt.sap official, abap: a CAP application with Fiori apps where the classification is maintained and the ATC findings exported from the system are read back per system.
A CAP application deployed into a Cloud Foundry subaccount and reached through a SAP Build Work Zone site, where the classification the ATC checkProject KernseifeA custom ABAP Test Cockpit check that scores how custom code uses SAP objects against a classification the customer writes, as a measure of clean core technical debt.sap official, abap scores against is written and where its findings are read. The Settings app does the initial setup, the customer details and the systems; the Jobs app takes the CSV exported from CDS view ZKNSF_I_EXPORT through its "Findings Import (CSV)" action against the system the run came from, and the imported development objects then appear in the Custom Code and Overview apps. The two halves meet in that file: the check runs in the ABAP system, and its findings reach the app as a CSV import. No standalone approuter is deployed — the integrated one inside Work Zone serves the apps, and a user sees them once assigned the site role and the kernseife-admin-${space} role. Where the BTP setup is out of reach, the same information can be read in the ABAP system from CDS view ZKNSF_I_DEVELOPMENT_OBJECTS.
Facts
Where it sits
Who is behind it
In the atlas: maintains 146, wrote 61@SAPmaintainerandreasmuensterContributes to this
In the atlas: contributes to 3@andreasmuensterDaniel HuserContributes to this
In the atlas: contributes to 3@daniel-huserLik WeiContributes to this
In the atlas: maintains 1, contributes to 5@likweitanLukas BretschneiderContributes to this
In the atlas: contributes to 2@LukasBretschneiderMarkus KapferContributes to this
In the atlas: contributes to 2@mrkskpfr5 contributors
Before choosing this
Conditions
PracticalFunctional boundary
There is no hosted tenant: the application is built from the repository and deployed into a subaccount of your own, which needs Cloud Foundry runtime memory, a HANA Cloud instance for an HDI container, five bound services and a SAP Build Work Zone subscription on the Standard (Application) plan. The ATC check works without it, and the maintainers note that deviating from the ratings they supply switches off features such as the default classification logic.
What it declares
Every artifact
- Type
- App
- Origin
- By SAP
As an app
- Where it runs
- does not say
- Distributed through
- does not say
Connections
Whether code can run in ABAP Cloud, and what to do when it cannot
Scales Cloud Foundry app instances by policy rules and schedules
OAuth server issuing JWTs and holding scopes for BTP apps
Cloud Foundry runtime of SAP BTP for polyglot applications
Role-based business site for SAP and third-party apps
OpenSearch-based store for logs, metrics and traces
Named, credentialed addresses of other systems resolved at runtime
Managed SAP HANA database service on BTP
Stores UI5 and HTML5 apps and serves them through the approuter
Collects Cloud Foundry or Kyma logs into a searchable Kibana
Custom ATC check scoring SAP object usage against your classification
Download
README
quoted from SAP/project-kernseife under Apache-2.0, readGetting Started
Welcome to Kernseife.
It contains these folders and files, following our recommended project layout:
| File or Folder | Purpose |
|---|---|
app/ | content for UI frontends goes here |
db/ | your domain models and data go here |
srv/ | your service models and code go here |
package.json | project metadata and configuration |
readme.md | this getting started guide |
Local development setup
1. VSCode setup
Download and install VSCode
Following VSCode extensions are recommended to be installed:
2. Node Version Manager
Make sure you have installed nvm (for installation guide see here)
If you run the project for the first time run nvm install to install the required Node version otherwise you can run nvm use to use the appropriate installed version.
3. Install project dependencies
npm ci
npm ci --prefix db
Dependency security maintenance
Use Node.js 24.18.0 (nvm use) for local development, matching the deployment workflow. Install
dependencies with npm ci in this directory; the HANA deployer has its own
lockfile in db/. Audit both with npm audit and npm audit --prefix db.
The root package overrides Lodash to a patched 4.x release and the UI5 Project
Pacote dependency to 22.0.1 with Sigstore 5.0.0. These address vulnerabilities
in the versions pinned by upstream build tooling. Keep the overrides until
upstream versions include those fixes, and validate all UI5 builds when changing
them. The unused UI5 JSDoc lint plugin was removed because it installed legacy
ESLint and vulnerable dependencies; linting uses the root eslint.config.mjs.
As of 26 October 2026, node-forge 1.4.0 remains affected by
GHSA-86w9-cpqp-85rv,
with no published patched version. It is pulled in by the Cloud SDK jks-js
dependency. Track the upstream fix and review destinations using JKS
certificates before rollout. An audit may consequently still report this
advisory and its dependent packages.
CAP development toolkit 10.2.0 also bundles body-parser 2.3.0, affected by GHSA-27r3-jxmh-p828. Although body-parser 2.4.0 is patched, npm overrides do not replace dependencies inside the toolkit's published bundle. This development-only dependency awaits a corrected toolkit release; the production server uses body-parser 2.4.0.
Dependency upgrade compatibility (26 October 2026)
All direct npm dependencies in the root, nine UI5 workspaces, and HANA deployer
are pinned to their latest stable releases checked on this date, except
TypeScript. TypeScript 6.0.3 is the latest supported by both ts-jest 29.4.15
(typescript <7) and typescript-eslint 8.72.0 (typescript <6.1); their peer
requirements prevent adopting TypeScript 7.0.2 yet. Transitive packages follow
the versions supported by their parent packages.
The update moves CAP to 10.2.1, HANA/SQLite adapters to 3.1.2, Express to 5.3.0,
Jest to 30.5.2, ESLint to 10.13.0, and UI5 runtime to 1.153.0. The CAP toolkit
is a local, pinned dependency, and deployment installs the lockfile with
npm ci. GitHub Actions and the Cloud Foundry CLI are updated as well.
Type generation and CAP type definitions are development dependencies, keeping
their optional toolkit peer out of the production server. Supported transitive
releases are refreshed and deduplicated, so CAP also uses Express 5.3.0.
CAP 10 requires Node 22 or newer. Its compiler maps the existing Int64 usage
counter to HANA BIGINT; the checked-in migration widens the existing INTEGER
column. Validate this migration on the deployed HANA database. CAP 10 also
serializes Decimal/Int64 database values as strings by default; check usage
counts, percentage displays, and import/export flows during application testing.
The deployment TypeScript configuration sets rootDir explicitly so compiled
handlers stay under gen/srv/srv, and removes the deprecated baseUrl option.
ESLint 10 findings are fixed by removing unused initial assignments and retaining
the cause of wrapped ZIP errors. The integration fixture supplies local types
for deployment/disconnect APIs omitted by cds-types 0.20.0.
Validation: clean Node 24 installs of both lockfiles; dependency tree without peer conflicts; application and test TypeScript checks; lint with zero errors; the complete MTA build, including all nine UI5 ZIPs and production installs; and a local smoke check of compiled server startup, all four OData metadata endpoints and collection reads, security/cache headers, and custom favicon handling. The smoke check uses SQLite and public release-state data, not deployed HANA/BTP connections.
Jest passes 28 of 30 tests. The two failures also occur with the unchanged
dependency versions: they incorrectly require CSV runId, which is optional.
Their correction is tracked separately in
PR #122. The HANA deployer
audit is clean; the application audit has the two upstream advisories described
above, reported through six affected packages (four in the production server).
Others providing
Compare all 14 on the ABAP Cloud readiness page →- abap-cloud-guiabap-cloud-guiA report-style programming model for abap2UI5: one class produces a selection screen with a WRITE list or an ALV grid, running as a UI5 app on ABAP Cloud as well as on NetWeaver 7.02.independent, abapReport-style programming model for abap2UI5 on ABAP Cloud
- codepagecodepageA polyfill class, ZCL_ABAP_CODEPAGE, that converts strings to binary and back behind one interface, where Clean Core blocks CL_ABAP_CODEPAGE and older systems lack CL_ABAP_CONV_CODEPAGE.independent, abapPolyfill for CL_ABAP_CODEPAGE under Clean Core
- Modernization Agents for SAP on AWSModernization Agents for SAP on AWSAWS's suite of agents for SAP modernisation work: custom ABAP converted for S/4HANA, PI/PO interfaces moved to Integration Suite, BW objects moved to SAP Datasphere, deployed into a customer's own AWS account and reached only after registration.partner, abapAWS agents for ABAP, PI/PO and BW modernisation work
- ROSAROSAAnswers whether an SAP object is released for ABAP Cloud, and what to use instead when it is not — served from SAP's own Cloudification Repository over MCP and over plain REST.independent, abapMCP server answering whether SAP objects are released for ABAP Cloud
- SAP Table to CDS MapperSAP Table to CDS MapperA standalone HTML report that ranks the candidate CDS objects for a classic SAP table or table field, from a field-lineage snapshot of an SAP S/4HANA 2025 FPS01 system.independent, abapRanked candidate CDS objects for a classic SAP table or field
- Cloudification RepositoryCloudification RepositorySAP's list of released APIs for SAP Cloud ERP, with the successors of the objects that are not released — the content the ABAP test cockpit's cloud readiness and clean core checks are pointed at.sap official, abapSAP's list of released APIs for SAP Cloud ERP with successors
- code pal for ABAP — Cloud Editioncode pal for ABAP — Cloud EditionThe same Clean ABAP check set for ABAP Cloud, where the legacy edition cannot run.sap official, abapClean ABAP check set for ABAP Cloud
- Project KernseifeProject KernseifeA custom ABAP Test Cockpit check that scores how custom code uses SAP objects against a classification the customer writes, as a measure of clean core technical debt.sap official, abapCustom ATC check scoring SAP object usage against your classification
- Clean-Core.ioClean-Core.ioA free hosted workspace that reads one piece of custom ABAP, redraws its business process as BPMN with a line anchor on every element, grades the SAP objects it uses Level A–D and ends in a keep, rebuild, move-to-standard or retire decision.independent, abapHosted workspace redrawing custom ABAP as BPMN and grading it
- Clean Core MeasurementClean Core MeasurementAn ABAP application for a central ATC system that imports Clean Core check results and reports them per system as Level A to D KPIs, technical debt scores and documented assignments.independent, abapReports Clean Core ATC results per system as Level A to D KPIs
- ABAP Select ConverterABAP Select ConverterConverts a classic Open SQL SELECT against dictionary tables to the equivalent statement against released Core Data Services entities and their fields.independent, abapConverts classic Open SQL SELECTs to released CDS entities
- abap-system-fieldsabap-system-fieldsAn ABAP Cloud class that wraps SY system fields and calendar-date functions behind an injectable instance, so code that reads them stays stable under unit tests.independent, abapInjectable wrapper for SY fields and date functions in ABAP Cloud
- Cloudification Repository ViewerCloudification Repository ViewerA browser form over the Cloudification Repository, the list SAP publishes of which standard objects are released for ABAP Cloud and what replaces the ones that are not.independent, abapBrowser form over SAP's Cloudification Repository for ABAP Cloud
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
History in the atlas
- First seen.
For your agent
- Ref
artifact:sap-project-kernseife-btp-app- JSON
- /artifacts/sap-project-kernseife-btp-app.json
- MCP
- Connecting an agent