Everything in the atlas
Type
Domain: 2
Origin
Signals
Content
More
Group by: None
XSUAA authentication stack for an MCP server on SAP BTP
It stops at the `AuthInfo` and the raw bearer token, and the README lists what stays with the consuming server: rate limiting, the scope and tool policy, the MCP transport, the SAP HTTP client's headers, and helmet-style hardening. The one piece of hardening it constrains rather than defers is the cross-origin opener policy, which it deliberately leaves unset because popup-based OAuth breaks under it. It is ESM-only on Node 22 or later and shares the host's Express and MCP SDK instances as peer dependencies, so a server on Express 4 cannot take it.
Business-level metrics from CDS annotations via @cap-js/telemetry
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
Transactional processing of asynchronous and periodic CAP events
If you need sub-second fan-out to external consumers this is the wrong layer — reach for [Event Mesh](artifact:btp-event-mesh) or Kafka. Without [Redis](external:redis), periodic processing still works but instant dispatch degrades to polling.
Live-updatable feature toggles for CAP, backed by Redis
CLI for operating tenants of multitenant CAP applications
CAP integration with the SAP Audit Log service
Generates Helm charts for the CAP Operator on Kubernetes
Change history for annotated CAP entities
CAP integration with SAP Data Privacy Integration
OpenTelemetry instrumentation for CAP services
Browser login and session module for SAP MCP servers
The maintainer states it is unofficial, not endorsed by SAP, and that it automates authenticated SAP web endpoints and browser session cookies in ways SAP's terms of service or an organisation's own policies may restrict. Password login is confined to `accounts.sap.com` and the standard SAP Cloud Identity Services tenant domains: a custom IAS domain, or a login that conditional authentication delegates to a corporate identity provider, fails closed before the password is filled and has to be completed through an interactive login instead.
Framework core: module loader, MVC runtime, binding, routing, theming
Tool completing a CAP project's deployment configuration
Tied to a specific training repository and last released August 2023. The repository the package declares has been deleted — verified against the GitHub API, not just a failed fetch. The package is still on npm, so it installs; the source it was published from is no longer readable, which is a harder thing to discover than a stale version number.
CAP plugin controlling CDS logger and OpenTelemetry log verbosity
VS Code Multi-Target Application tools
Library for sending usage telemetry data
Authorization from DCL policies for Node.js apps on SAP Cloud Identity
Compiler from AMS DCL policies to DCN for local runs and tests
Its own account of itself is local running and tests: the DCN it writes serves as input for running an application using AMS on the DCL bundle locally. It carries the SAP Developer License Agreement rather than an open-source licence, and the repository named in its package metadata is an internal SAP host, so the npm page is the only thing to read.
SAP's Node.js application router in front of business applications
MTA generation and Cloud Foundry deploy for VS Code workspaces
A library a VS Code extension calls, not something installed and run on its own; there is no documented standalone CLI. No public repository either, so what it does is read from its own README rather than checked against source.
CAP Node.js runtime
Command line client and development toolkit for CAP
Multitenancy, tenant provisioning and extensibility for CAP
WebAssembly sandbox for tenant-specific extension code in CAP
SAP Passport handling for Node.js components
CLI to build, deploy, migrate and validate MDK projects
Specific to MDK metadata projects — nothing here builds or deploys a CAP service or a plain Fiori app. Closed-source, under SAP's own developer licence rather than a public repository.
Token validation and security context for XSUAA and IAS
Log fetcher and parser for one Cloud Foundry app
Read-only query tool for metrics in SAP Cloud Logging
Read-only query tool for OpenTelemetry spans in SAP Cloud Logging
Merged log tail of every started app in a Cloud Foundry space
OAuth2 token fetcher for a Cloud Foundry app's XSUAA binding
Library for managing ABAP constants from registered sources
Quiet No published releases; repository quiet for 41 months.
Functional boundary Not in a production environment yet: the maintainer puts abaK in beta, says its API can still change and more tests are needed, and asks that a non-beta release be waited for.
VS Code extension editing ABAP systems over ADT as a filesystem
Converts classic Open SQL SELECTs to released CDS entities
In beta by its own page's account, where conversion bugs may occur and not all functions and variants are supported yet. The shapes named as not yet supported are sub selects, FOR ALL ENTRIES, functions such as count and sum, and the IN operator with a value list, so a statement built on one of those is outside what the converter sets out to do.
TypeScript library reaching ABAP service instances on Cloud Foundry
Generates signed JSON Web Tokens in ABAP
No published releases; repository quiet for 68 months.
Object-oriented wrapper around the Business Application Log
CLI that pulls and pushes ABAP packages as local files over ADT
A Python 3.10+ CLI, installed with pipx rather than through any SAP-provided package manager. Its own README lists what it does not do yet: where-used, syntax check and unit test runs — for those it says to reach for [ADT/Eclipse](external:eclipse) or an MCP server. First release, v0.1.0, and no standalone LICENSE file in the repository — the MIT grant is in the README and in pyproject.toml's project metadata rather than its own file.
No published releases; repository quiet for 58 months.
Report-style programming model for abap2UI5 on ABAP Cloud
Not a way to run existing reports unchanged: a report is rewritten as a class, and `CALL SCREEN`, dynpro modules, batch input, `SUBMIT` and native SQL are refused by the converter rather than mapped. Not an SAP GUI in the browser either: the programming model is classic and the screens are UI5, and the README points at abap2UI5-addons/sapgui for SE16N or SM37. Output has gaps the README names — ALV cells show dates and times as the model carries them rather than in the user's format, print is a text file because ABAP Cloud has no spool, and value tables for F4 are read on premise only.
Chainable logger for ABAP Cloud around CL_BALI_LOG
Validation library for ABAP checking dates, emails and GUIDs
No published releases; repository quiet for 40 months.
Framework for runtime parameters, ranges and value mappings in ABAP
Feature toggle for ABAP read via is_active on view ZFEAT_TOGGLE
Fluentd client in ABAP for sending log lines to a collector
No published releases; repository quiet for 96 months.
Logger storing RFC function module call parameters as JSON
Generic customizing table and reader for ad hoc ABAP parameters
ABAP logging library with one interface across output targets
No published releases; repository quiet for 36 months.
Exports Business Application Log entries to Graylog or Loki
No published releases; repository quiet for 41 months.
Logging library for ABAP over the Application Log
Message logger for ABAP Cloud that saves to the Application Log
Exposes ABAP stack metrics to a monitoring tool
The declared repository is archived.
OTLP serialisation of traces, metrics and logs in ABAP
Framework activating custom ABAP enhancements through a Fiori app
Anything below SAP S/4HANA 2023 FPS03 (ABAP 7.58), and any system not running the ABAP Cloud development model: those two are the prerequisites the README names, and it states that the framework targets ABAP Cloud exclusively.
Framework for multi-step ABAP processes with monitoring
Only on SAP S/4HANA 2023 and 2025, on premise or private cloud: [SAP S/4HANA Cloud, Public Edition](external:sap-s4hana-cloud-public-edition) and the [SAP BTP ABAP environment](artifact:btp-abap-environment) are listed as coming soon, and a 2023 system has to leave out `ZABAP_PRC_EVENTS_SE_2025`, whose event-based side effects rely on APIs released with S/4HANA 2025. Not for a system that already carries a copy, because object names are global and two versions cannot live side by side, and not for a productive system by way of the `ZABAP_PRC_DEMO*` packages, which the README states are not intended for one and whose init classes delete and rebuild their own tables on every run. While the major version is 0 the public API is not stable: minor bumps carry breaking changes with no deprecation period, so productive use means pinning a tag and reading the CHANGELOG before every upgrade.
Prometheus client for ABAP, installed with abapGit
No published releases; repository quiet for 39 months.
Checks passwords against Have I Been Pwned from ABAP
Injectable wrapper for SY fields and date functions in ABAP Cloud
Helper class for reading TVARVC parameters and select-options
No published releases; repository quiet for 33 months.
ABAP API for OAuth 2.0 authentication
No published releases; repository quiet for 97 months.
Checks field values against domain fixed values and check tables
No published releases; repository quiet for 54 months.
Promise and async/await implementation for ABAP
No published releases; repository quiet for 36 months.
HTTP NTLM client for ABAP
OA2C_SPECIFICS implementation for Microsoft Azure OAuth 2.0 in ABAP
No published releases; repository quiet for 27 months.
Framework for running ABAP work units in parallel tasks
Quiet No published releases; repository quiet for 57 months.
Functional boundary The maintainer states the current state has never been used in real-world scenarios: the demo reports in package ZAPS_DEMO and the unit tests are the only runs reported, and the release table marks SAP_BASIS 740 unclear, 754 as the release it was developed on, and 750 to 756 as expected to work.
OpenPGP implementation in ABAP, scoped to signing
Not for anything important, which is the maintainer's own instruction: the README's Warning section calls it stupid to write your own encryption or PGP library, says abapPGP will most certainly contain severe bugs, and points instead at established PGP software such as [OpenPGP](http://openpgp.org/). Signing is the only scope it states.
Class-based wrapper around STRUST certificate management
SAP GUI transaction for one-click transports of copies
VS Code extension automating ActiveControl transport forms
Usage, error and response-time monitor for abap2UI5
It sees [abap2UI5](artifact:abap2ui5-abap2ui5) only: the figures come from the framework's HTTP handler, its monitor hook and its draft table, so nothing outside abap2UI5 appears in them. The usage, error and performance tabs stay empty until the handler line is in place or the user exit sets `check_monitor_active`. Recording which employee used which application, when and how fast, is subject to works council co-determination in Germany (§ 87 (1) no. 6 BetrVG); user tracking is `HASH` by default, `NAME` stores user names, and the request recorder keeps the complete request and response of every roundtrip for two days by default.
Injects the Dynatrace agent into Java applications on SAP BTP
API proxies with security and traffic policies and Developer Hub
Scales Cloud Foundry app instances by policy rules and schedules
Tracks vulnerabilities in open-source components of BTP apps
ABAP application options as a structure with a generated editor
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 app and CAP service copying role collections between subaccounts
Quiet No published releases; repository quiet for 54 months.
No license Neither the package manifest nor the repository tree declares a licence.
BTP Core Services as MCP tools with in-chat dashboards
It administers a real account through Core Services, so what it can change is what the caller can change. And the UI half depends on hosts that render mcp-ui or MCP Apps resources; elsewhere those five tools return markup nobody displays.
Containerised script setting up an SAP BTP account from JSON config
The declared repository is archived.
RAP sales order using number ranges, change documents and Adobe forms
Postman collections for the SAP Analytics Cloud SCIM API
Which CAP paths trigger @assert.target and which do not
Neither the package manifest nor the repository tree declares a licence.
CAP services and a UI for trying role restrictions with mock users
Neither the package manifest nor the repository tree declares a licence.
MTA projects sharing a role collection across role templates
Neither the package manifest nor the repository tree declares a licence.
CAP bookshop with Fiori elements UI deployed whole to Cloud Foundry
Neither the package manifest nor the repository tree declares a licence.
CAP bookshop wired to the Authorization Management Service
Neither the package manifest nor the repository tree declares a licence.
Terraform samples for the SAP BTP Administrator's Guide account model
Getting-started guide for a Hello-World function on SAP BTP, Kyma
Guide and samples for moving Java apps from Neo to Cloud Foundry
Code samples for the Getting Started with Terraform on SAP BTP course
Samples for the Terraform Provider for SAP BTP
UI5 app reading the signed-in user via launchpad and approuter
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The repository publishes no licence, so reusing its code needs the author's permission.
CAP microservice on XSUAA managing users and authorizations