Everything in the atlas
Type
Domain: 2
Origin
Signals
More: 3
Group by: Capability
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 plugin watching Cardano addresses and emitting events
CAP Node.js runtime
Stores, browses and resends messages a CAP service receives
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.
Maven bill of materials pinning CAP Java module versions
CAP Node.js runtime
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.
Yeoman generator for Cloud Connector mappings and BTP destinations
Destination resolution and axios calls from CAP configuration
Release and repository quiet for 46 months.
Remote Services for consuming OData V2 and V4 APIs in CAP Java
SAP Cloud SDK integration for remote REST services in CAP Java
CAP project reaching S/4 via SAP BTP Private Link Service for Azure
Neither the package manifest nor the repository tree declares a licence.
CAP service serving Northwind's external OData Products as its own
CAP service actions calling OpenAI chat completions two ways
Neither the package manifest nor the repository tree declares a licence.
CAP Java service calling role collection APIs via a generated client
Neither the package manifest nor the repository tree declares a licence.
On-premise ABAP OData V2 service read from CAP over Connectivity
Neither the package manifest nor the repository tree declares a licence.
CAP Node.js action calling BAPI_EPM_BP_CREATE over RFC
Neither the package manifest nor the repository tree declares a licence.
MTA deploying CAP, HDI container and a Fiori elements app
Spring Boot apps routing AWS SDK traffic over SAP Private Link
Prints documents held in CAP entities through SAP Print service
CAP plugin wrapping the SAP Forms service by Adobe on BTP
CAP integration with SAP Integration Suite advanced event mesh
Exports AsyncAPI documents for a CAP service's events
Consumes events from SAP Cloud Application Event Hub in CAP
CAP Node.js runtime
Stores, browses and resends messages a CAP service receives
Kafka adapter exposing topics as a CDS messaging service
CAP Java plugin for SAP Integration Suite, advanced event mesh
Connects CAP Java messaging to SAP Event Mesh
Connects CAP Java messaging to SAP Cloud Application Event Hub
Connects CAP Java messaging to Apache Kafka
Beta connector from CAP Java messaging to Redis Pub/Sub
Maven bill of materials pinning CAP Java module versions
Event-driven RAG app with CAP, Cloud Integration and SAP HANA Cloud
Neither the package manifest nor the repository tree declares a licence.
CAP and Fiori elements app for managing Cloud Integration datastores
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.
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.
Business notifications from CAP Java via SAP Alert Notification
Calls to ABAP function modules over RFC from a CAP service
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.
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.
CAP Node.js action calling BAPI_EPM_BP_CREATE over RFC
Neither the package manifest nor the repository tree declares a licence.
CAP Node.js runtime
Maven bill of materials pinning CAP Java module versions
CAP Node.js runtime
Command line client and development toolkit for CAP
Data federation for CAP via delegation, caching and replication
Remote Services for consuming OData V2 and V4 APIs in CAP Java
CAP services and a UI for trying role restrictions with mock users
Neither the package manifest nor the repository tree declares a licence.
CAP service serving Northwind's external OData Products as its own
CAP Java service consuming a Business Partner API mocked in Node.js
Neither the package manifest nor the repository tree declares a licence.
CAP service actions calling OpenAI chat completions two ways
Neither the package manifest nor the repository tree declares a licence.
On-premise ABAP OData V2 service read from CAP over Connectivity
Neither the package manifest nor the repository tree declares a licence.
CAP Java plugin sending audit log events to SAP Audit Log service
CAP Java handler for SAP Audit Log service API version 2
Maven bill of materials pinning CAP Java module versions
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.
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.
SAP's Node.js application router in front of business applications
CAP Node.js runtime
Token validation and security context for XSUAA and IAS
TypeScript library reaching ABAP service instances on Cloud Foundry
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.
OAuth2 token validation from XSUAA and SAP Cloud Identity Services
Former XSUAA JWT validation for CAP Java, removed in CAP Java 3.0
CAP services and a UI for trying role restrictions with mock users
Neither the package manifest nor the repository tree declares a licence.
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.
CAP Node.js runtime
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.
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.
Maven bill of materials pinning CAP Java module versions
CAP services and a UI for trying role restrictions with mock users
Neither the package manifest nor the repository tree declares a licence.
CAP Java authorization checks tried case by case
Neither the package manifest nor the repository tree declares a licence.
Change history for annotated CAP entities
Change log of annotated entity fields for CAP Java
CAP Node.js runtime
CAP Node.js runtime
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.
Custom messages and handler classes for CAP input validation
Zod schemas as CAP validation middleware
Maven bill of materials pinning CAP Java module versions
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.
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.
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.
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.