onedevatlasBeta
Browse the atlas
AllABAPBTPCAPUI5
AppApptypeAn application you deploy and use, installed into a system or loaded into an application as a component, rather than a library whose functions you call.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

Kernseife BTP App

The BTP side of Project Kernseife: 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 check 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.

GitHub99 ★
Docs

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
ABAP
Provides
ABAP Cloud readinessABAPABAP Cloud readinesscapabilityWhether code can run in ABAP Cloud — released APIs only, no direct table access, no obsolete statements — and what to do with the code that cannot.
Part of
Project KernseifeProject KernseifeartifactA 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.
Serves
BTP/BAIP
Requires
SAP BTP, Cloud Foundry RuntimeSAP BTP, Cloud Foundry RuntimeartifactThe runtime the application is deployed into: a subaccount with Cloud Foundry enabled and at least 2 GB of application runtime.SAP HANA CloudSAP HANA CloudartifactThe database behind the application: an instance that can host the HDI container the db module is deployed into, bound on the hdi-shared plan.SAP Authorization and Trust Management serviceSAP Authorization and Trust Management serviceartifactThe authentication and the roles behind the apps, bound on the application plan; version 1.5.0 changed the authorizations the BTP app uses.SAP HTML5 Application Repository service for SAP BTPSAP HTML5 Application Repository service for SAP BTPartifactWhere the built Fiori apps are stored, bound on the app-host plan and picked up in Work Zone's Channel Manager and Content Explorer.SAP Destination serviceSAP Destination serviceartifactOne of the services the installation guide lists as required, on the lite plan.Application AutoscalerApplication AutoscalerartifactOne of the services the installation guide lists as required, on the standard plan.SAP Cloud LoggingSAP Cloud LoggingartifactWhere the application's logs go, on the dev plan, with the standard plan named for production.SAP Build Work Zone, standard editionSAP Build Work Zone, standard editionartifactThe site the apps are published to and the entry point in front of them: the guide deploys no standalone approuter and uses the one integrated in Work Zone, on the Standard (Application) plan.
Optional
SAP Application Logging service for SAP BTPSAP Application Logging service for SAP BTPartifactThe logging service the guide states is still supported where the deployment uses it instead of Cloud Logging.logging

Who is behind it

SAPSAPOrganisationMaintains this
In the atlas: maintains 142, wrote 14@SAPmaintainerandreasmuensterPersonContributes to this
In the atlas: contributes to 3@andreasmuensterDaniel HuserPersonContributes to this
In the atlas: contributes to 3@daniel-huserLik WeiPersonContributes to this
In the atlas: maintains 1, contributes to 5@likweitanLukas BretschneiderPersonContributes to this
In the atlas: contributes to 2@LukasBretschneiderMarkus KapferPersonContributes 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

Connections11

Download
Kernseife BTP App connectionsKernseife BTP AppPROVIDES→ provides1provides stated Holds the custom classification that the ATC check scores against and produces its JSON file, and imports the findings of a check run as CSV per system, showing each development object and its level in the Custom Code and Overview apps. SAP/project-kernseife Wiki — ABAP Installation Guide, Upload Classification Json: https://github.com/SAP/project-kernseife/wiki/ABAP-Installation-Guide SAP/project-kernseife Wiki — Scoring & Development Object Guide: https://github.com/SAP/project-kernseife/wiki/Scoring-&-Development-Object-Guide SAP/project-kernseife Wiki — Scoring & Development Object Guide: https://github.com/SAP/project-kernseife/wiki/Scoring-&-Development-Object-GuideABAP Cloud readinessNEEDS→ needs8needs stated One of the services the installation guide lists as required, on the standard plan. SAP/project-kernseife Wiki — BTP Installation Guide, Required Services: https://github.com/SAP/project-kernseife/wiki/BTP-Installation-GuideApplication Autoscalerneeds stated The authentication and the roles behind the apps, bound on the application plan; version 1.5.0 changed the authorizations the BTP app uses. SAP/project-kernseife Wiki — BTP Installation Guide, Required Services: https://github.com/SAP/project-kernseife/wiki/BTP-Installation-Guide SAP/project-kernseife Wiki — BTP Installation Guide, Post-Deployment Setup: https://github.com/SAP/project-kernseife/wiki/BTP-Installation-GuideSAP Authorization and Trust Managementserviceneeds stated The runtime the application is deployed into: a subaccount with Cloud Foundry enabled and at least 2 GB of application runtime. SAP/project-kernseife Wiki — BTP Installation Guide, Required BTP Resources: https://github.com/SAP/project-kernseife/wiki/BTP-Installation-GuideSAP BTP, Cloud Foundry Runtimeneeds stated The site the apps are published to and the entry point in front of them: the guide deploys no standalone approuter and uses the one integrated in Work Zone, on the Standard (Application) plan. SAP/project-kernseife Wiki — BTP Installation Guide, Required Subscriptions: https://github.com/SAP/project-kernseife/wiki/BTP-Installation-Guide SAP/project-kernseife Wiki — BTP Installation Guide, SAP Build Work Zone Configuration: https://github.com/SAP/project-kernseife/wiki/BTP-Installation-GuideSAP Build Work Zone, standard editionneeds stated Where the application's logs go, on the dev plan, with the standard plan named for production. SAP/project-kernseife Wiki — BTP Installation Guide, Required Services: https://github.com/SAP/project-kernseife/wiki/BTP-Installation-GuideSAP Cloud Loggingneeds stated One of the services the installation guide lists as required, on the lite plan. SAP/project-kernseife Wiki — BTP Installation Guide, Required Services: https://github.com/SAP/project-kernseife/wiki/BTP-Installation-GuideSAP Destination serviceneeds stated The database behind the application: an instance that can host the HDI container the db module is deployed into, bound on the hdi-shared plan. SAP/project-kernseife Wiki — BTP Installation Guide, Required BTP Resources: https://github.com/SAP/project-kernseife/wiki/BTP-Installation-Guide SAP/project-kernseife Wiki — BTP Installation Guide, Required Services: https://github.com/SAP/project-kernseife/wiki/BTP-Installation-GuideSAP HANA Cloudneeds stated Where the built Fiori apps are stored, bound on the app-host plan and picked up in Work Zone's Channel Manager and Content Explorer. SAP/project-kernseife Wiki — BTP Installation Guide, Required Services: https://github.com/SAP/project-kernseife/wiki/BTP-Installation-GuideSAP HTML5 Application Repositoryservice for SAP BTP→ optionally needs1optionally needs stated If: the legacy Application Logging service is bound in place of Cloud Logging The logging service the guide states is still supported where the deployment uses it instead of Cloud Logging. SAP/project-kernseife Wiki — BTP Installation Guide, Required Services: https://github.com/SAP/project-kernseife/wiki/BTP-Installation-GuideSAP Application Logging service for SAPBTPifLINEAGE→ part of1part of stated SAP/project-kernseife — README, release note: https://github.com/sap/project-kernseife SAP/project-kernseife Wiki — Home: https://github.com/SAP/project-kernseife/wikiProject Kernseife

README

quoted from SAP/project-kernseife under Apache-2.0, read
SAP/project-kernseife/btp/README.mdOn GitHub

Getting Started

Welcome to Kernseife.

It contains these folders and files, following our recommended project layout:

File or FolderPurpose
app/content for UI frontends goes here
db/your domain models and data go here
srv/your service models and code go here
package.jsonproject metadata and configuration
readme.mdthis 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 global packages (e.g. CAP's cds-dk and TypeScript)
npm i -g @sap/cds-dk typescript ts-node

Dependency security maintenance

Use Node.js 22 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 21.5.1 with Sigstore 4.1.1. 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.

Apache-2.0, read

Others providing13

Compare all 14 on the ABAP Cloud readiness page →
ABAP Cloud readiness
  1. abap-cloud-guiReport-style programming model for abap2UI5 on ABAP Cloudfrom ABAP
  2. codepagePolyfill for CL_ABAP_CODEPAGE under Clean Corefrom ABAP
  3. Modernization Agents for SAP on AWSAWS agents for ABAP, PI/PO and BW modernisation workfrom ABAP
  4. ROSAMCP server answering whether SAP objects are released for ABAP Cloudfrom ABAP
  5. SAP Table to CDS MapperRanked candidate CDS objects for a classic SAP table or fieldfrom ABAP
  6. Cloudification RepositorySAP's list of released APIs for SAP Cloud ERP with successorsfrom ABAP
  7. code pal for ABAP — Cloud EditionClean ABAP check set for ABAP Cloudfrom ABAP
  8. Project KernseifeCustom ATC check scoring SAP object usage against your classificationfrom ABAP
  9. Clean-Core.ioHosted workspace redrawing custom ABAP as BPMN and grading itfrom ABAP
  10. Clean Core MeasurementReports Clean Core ATC results per system as Level A to D KPIsfrom ABAP
  11. ABAP Select ConverterConverts classic Open SQL SELECTs to released CDS entitiesfrom ABAP
  12. abap-system-fieldsInjectable wrapper for SY fields and date functions in ABAP Cloudfrom ABAP
  13. Cloudification Repository ViewerBrowser form over SAP's Cloudification Repository for ABAP Cloudfrom ABAP

Details

Sources3
GitHub APIdiscovered herechecked
github.com/SAP/project-kernseife/tree/main/btptree, pushes, contributors, CIchecked
btp/README.mdquoted, and what the entry declareschecked

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
discovered viaGitHub API
first seen in the atlas
ecosystem and domainabap, operations-and-runtime
Contributors5
andreasmuensterDaniel HuserLik WeiLukas BretschneiderMarkus Kapfer

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:sap-project-kernseife-btp-app
JSON
/artifacts/sap-project-kernseife-btp-app.json
MCP
Connecting an agent