Everything in the atlas
Type
Domain: 3
Origin
Signals
Content
More
Group by: Kind
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.
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.
SDK for SAP Advanced Financial Closing scheduling providers on CDS
CAP integration with SAP Integration Suite advanced event mesh
Exports AsyncAPI documents for a CAP service's events
CAP integration with the SAP Audit Log service
Change history for annotated CAP entities
CAP integration with SAP Data Privacy Integration
Consumes events from SAP Cloud Application Event Hub in CAP
Triggers n8n workflows from a CAP application
Business notifications from CAP to SAP Build WorkZone
Prints documents held in CAP entities through SAP Print service
Starts and manages SAP Build Process Automation processes from CAP
Renamed copy of @cap-js/notifications under another scope
Release and repository quiet for 24 months.
Annotation-driven mail on CAP entity lifecycle events
Node below 22, or [@sap/cds](artifact:sap-cds) below 9: the package declares the first in engines and the second as a peer dependency. Any mail path other than Microsoft Graph, until a provider is written for it: graph is the only kind that sends, and basic, the kind configured by default, is the base class such a provider extends.
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.
Copy of @cap-js/notifications published under another scope
Reach for the original unless you know why you are not. This is a republished copy rather than a fork with a direction of its own: the README points at cap-js/notifications for the details, and nothing here says what was changed or why.
CAP plugin watching Cardano addresses and emitting events
CAP plugin wrapping the SAP Forms service by Adobe on BTP
Destination lookup and connectivity proxy for the Cloud SDK
HTTP client carrying a destination's credentials
Shared machinery under the Cloud SDK's OData and OpenAPI clients
Generated OpenAPI clients for the Cloud SDK
Timeouts, retries and circuit breaking around remote calls
General utilities shared across the Cloud SDK packages
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
CAP Node.js runtime
ISO content for CAP's countries, languages, currencies and timezones
Command line client and development toolkit for CAP
Calls to ABAP function modules over RFC from a CAP service
Token validation and security context for XSUAA and IAS
Node module for CAP calling external APIs through a destination
Quiet Release and repository quiet for 57 months.
Functional boundary The package declares `@sap/cds` ^4.5.2 among its dependencies and pins `@sap-cloud-sdk/core` at 1.37.1, so a project on CAP 5 or later is outside the range it states.
OAuth2 token fetcher for a Cloud Foundry app's XSUAA binding
TypeScript library reaching ABAP service instances on Cloud Foundry
JSON adapter exposing ABAP function modules over HTTP
Input arrives only as JSON, or as plain XML if the ABAP built-in transformation is switched on, whatever the output format is set to. Cross-site calls are limited to JSONP: the maintainer lists CORS support as planned.
Generates signed JSON Web Tokens in ABAP
No published releases; repository quiet for 68 months.
No published releases; repository quiet for 58 months.
Validation library for ABAP checking dates, emails and GUIDs
No published releases; repository quiet for 40 months.
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.
Checks passwords against Have I Been Pwned from ABAP
ABAP API for OAuth 2.0 authentication
No published releases; repository quiet for 97 months.
Library that reads and generates Excel spreadsheets from ABAP
Checks field values against domain fixed values and check tables
No published releases; repository quiet for 54 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.
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
RFC-callable ABAP API for SAP data extraction for ADELE
No published releases; repository quiet for 73 months.
Fiori launchpad notification for application log errors
ABAP classes sending push notifications to Mobile Services
No published releases; repository quiet for 54 months.
Business data graph queried with OData V4 or GraphQL
API proxies with security and traffic policies and Developer Hub
Tracks vulnerabilities in open-source components of BTP apps
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.
Yeoman generator for Cloud Connector mappings and BTP destinations
Integration of CAP with n8n workflows and triggers
Utility bundle for CAP handlers: builder, roles, validation, queries
It is a bundle rather than a plugin with one job, and a single release from March 2026 — depending on it for the query helpers brings the auth and validation layers too.
Prebuilt SAP S/4HANA integration package for CAP projects
Custom messages and handler classes for CAP input validation
Azure AD and Azure AD B2C authentication strategy for CAP
Last released January 2022 at 0.0.21, against a passport strategy Microsoft has since deprecated.
JWT authentication for CAP without xsuaa or xssec
Last released April 2022 at 0.0.2, and no repository is declared on the package.
Data federation for CAP via delegation, caching and replication
Maps Microsoft Entra ID groups and app roles onto cds.User roles
Quiet Release and repository quiet for 25 months.
Functional boundary It performs no authentication flow of its own. The app must already be protected by Entra ID OAuth 2.0 at the App Service level; this only maps the resulting claims. It is explicitly not intended to run locally.
Stores, browses and resends messages a CAP service receives
Kafka adapter exposing topics as a CDS messaging service
NATS messaging service for the CAP Node.js runtime
Last released December 2022. Nothing says it fails on current cds, but nothing says it was tried either. 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.
Rate-limit pattern for CAP Node.js applications
Last released January 2024 at 0.0.6. 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.
Zod schemas as CAP validation middleware
Destination resolution and axios calls from CAP configuration
Release and repository quiet for 46 months.
CDS plugin for OData change tracking in CAP applications
ABAP connector to Kafka through the Confluent Kafka REST Proxy
No published releases; repository quiet for 57 months.
SAP's on-premises agent linking SAP BTP to customer-network systems
Identity Authentication and Identity Provisioning as one tenant
Builds and runs integration flows between cloud and on premise
Guided workflow for configuring SAP cloud solution integration
CAP Java plugin for SAP Integration Suite, advanced event mesh
CAP Java plugin sending audit log events to SAP Audit Log service
CAP Java handler for SAP Audit Log service API version 2
Change log of annotated entity fields for CAP Java
Connects CAP Java messaging to SAP Event Mesh
Connects CAP Java messaging to SAP Cloud Application Event Hub
Declarative status-transition flows on bound actions in CAP Java
OAuth2 token validation from XSUAA and SAP Cloud Identity Services
Connects CAP Java messaging to Apache Kafka
Triggers n8n workflows from CAP Java through the outbox
Business notifications from CAP Java via SAP Alert Notification
Beta connector from CAP Java messaging to Redis Pub/Sub
Remote Services for consuming OData V2 and V4 APIs in CAP Java
Former XSUAA JWT validation for CAP Java, removed in CAP Java 3.0
SAP Cloud SDK integration for remote REST services in CAP Java
Maven bill of materials pinning CAP Java module versions
TypeScript decoder for MYSAPSSO2 logon tickets
ABAP helper class building HTML emails from templates
Quiet No published releases; repository quiet for 52 months.
Functional boundary On an SAP S/4HANA system the maintainer points elsewhere: the README calls this solution helpful for non-S/4 systems and names SAP's own e-mail templates with CDS views as what S/4 systems have instead.
DuckDB extension reading SAP ERP tables, CDS views and BW queries
DataZoo GmbH calls the extension experimental and states that minimal testing and benchmarking were done. The Business Source License 1.1 it carries restricts offering the software to third parties on a hosted or embedded basis, so an embedding product needs a commercial licence. Telemetry is on by default and is switched off per session with `SET erpl_telemetry_enabled = false` or for the machine with `DATAZOO_DISABLE_TELEMETRY=1`.
RFC client for Node.js and TypeScript without the NW RFC SDK
BUSL-1.1 rather than node-rfc's Apache-2.0, so a product you distribute has to be read against the licence and its Additional Use Grant first, and the source is closed: the GitHub repository is the issue tracker and the documentation, nothing else. `RfcServerOptions.bgRfcHandlers` raises instead of accepting handlers, so a server receiving inbound bgRFC units is outside what this does. An ABAP `MESSAGE`-raised failure still arrives with its T100 template rather than the rendered sentence, and the dump name is not reported as `key` for that case.
Managed queues and topics over AMQP, MQTT and REST
ICF handler receiving Amazon SNS notifications in an ABAP system
No published releases; repository quiet for 64 months.
Single-file Handlebars templating for ABAP 7.40 SP02 and up
Blowfish cipher in ABAP, ECB and CBC modes
No published releases; repository quiet for 83 months.
B2B interface and mapping specification in Integration Suite
Java Swing tool maintaining Partner Directory entries for the Pipeline
Rule-based resolution of SAP S/4HANA business situations
MQTT 3.1.1 client implemented in ABAP
No published releases; repository quiet for 68 months.
MQTT publish/subscribe in ABAP with an external broker bridge
Quiet No published releases; repository quiet for 75 months.
Functional boundary The maintainer calls the project beta, states there are no experiences with productive usage, and leaves productive use at your own risk. Two further conditions are stated: the implementation used a NetWeaver ABAP stack 7.50 and a 7.40 was not tested, and a system user has to be maintained for the websocket services, because the external websocket tools do not support user-based authorization.
OAuth 2.0 grant flows for applications and APIs in Neo regions
Prebuilt connectors to non-SAP cloud applications as REST APIs
Standalone PDF generator written in ABAP
SDK-free TypeScript client for SAP synchronous RFC on Node.js
The maintainer states 0.x is beta with no production SLA, and scopes support deliberately narrowly: direct application-server transport, classic serialization and password authentication on S/4HANA 2023 and NetWeaver 7.50. Anything outside that is untested rather than unsupported.
RSS feed publisher for content from an SAP NetWeaver ABAP system
No published releases; repository quiet for 93 months.
Forwards abap2UI5 roundtrips to another system over RFC
For an app that calls `client->set_session_stateful( )`, which needs the ICF session of the system it runs on; apps keeping their state in the draft table, the abap2UI5 default, work unchanged. For an app that reads a request header through the user exit on the source system, because the consumer forwards method, body, path, query string and status, not headers.
SQL templates for HANA audit policies of an S/4HANA tenant
Ingests and retains compliance audit data from BTP
OAuth server issuing JWTs and holding scopes for BTP apps
Low-code and no-code tool for business processes and RPA bots
Distributes business events between SAP cloud applications
Provisioning jobs carrying users and groups between systems
Proxy from cloud apps to on-premise systems via Cloud Connector
Vault for an application's passwords, keys and keyrings
Serves BTP applications under the customer's own domain
Registration, login and consent for customer-facing sites
APIs for retention, deletion and personal data reports
Retention rules triggering blocking, deletion and archiving
Named, credentialed addresses of other systems resolved at runtime
Adobe Document Services on BTP for print and interactive PDFs
Integration service on BTP with Cloud Integration and API Management
Event streaming and management platform in Integration Suite
Event broker inside SAP Integration Suite
Key and certificate repository in SAP BTP's Neo data centres
Scans uploaded files over REST with ClamAV
Service answering data subjects about their stored personal data
Print queues between cloud applications and local printers
Private network link between a BTP service and a partner cloud
Resolves who is responsible for a process or item, and notifies them
Submits an ABAP report to the spool and converts the output to PDF
CAP plugin validating input against @Validator JSON Schema rules
Quiet Release and repository quiet for 30 months.
Functional boundary The annotation sits on a single element, so a rule that spans two fields, or one that needs a lookup, has nowhere in it to go.
Authority check helper class used across SchwarzIT's USI reports
Docker Compose IoT edge stack that connects to SAP BTP
No published releases; repository quiet for 63 months.
AES and Rijndael encryption utilities for ABAP
CAP and SAPUI5 demo of recovery from a supply disruption
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The data is illustrative: availability is binary and backup capacity unlimited, and the model carries no inventory; nothing in it is forecast or priced. The recall half runs only against classic ABAP, because its openCypher trace goes through ADBC, which is not released for ABAP Cloud, and it expects an SSH tunnel to the A4H system it was built against. A plain `npm start` passes no model key, so the agent cannot be used on a server started that way.
Partner profiles and agreements for B2B exchange in Integration Suite
ABAP template engine for Excel, Word, HTML and PDF
ABAP class filling a tagged Word .docx template with data
No published releases; repository quiet for 33 months.
Standalone ABAP class drawing PDFs without Adobe Document Server
Updater for root CAs in SAP NetWeaver from Mozilla's certificate store
Not where the system must not trust whatever the source trusts: the README states that you must trust the source, currently Mozilla, because the system can then reach every website holding a certificate generated by a root CA that source supplies. It installs those root CAs automatically, and the maintainer marks the tool use at own risk.