Everything in the atlas
Type
Domain: 2
Origin
Signals: Last 30 days
More: CAP
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 Node.js runtime
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
CAP Node.js runtime
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
CAP Java plugin for SAP Integration Suite, advanced event mesh
Connects CAP Java messaging to SAP Cloud Application Event Hub
Business notifications from CAP to SAP Build WorkZone
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
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.
Calling ABAP function modules over RFC from a CAP service
Neither the package manifest nor the repository tree declares a licence.
CAP Node.js runtime
Composite CAP app from separately deployed services
CAP travel-booking app built on xflights master data
CAP Node.js runtime
Command line client and development toolkit for CAP
CAP reuse package serving Airlines, Airports and Flights data
CAP travel-booking app built on xflights master data
Command line client and development toolkit for CAP
GitHub Action setting up the Cloud Foundry CLI
Consumer side of a CAP Java parent pom promotion model with Renovate
Neither the package manifest nor the repository tree declares a licence.
Connects a running CAP application to the CAP console
Inspects database entities and contents at CAP service level
Command line client and development toolkit for CAP
Connects a running CAP Java app to CAP console for monitoring
Language server for CDS
OData annotation features for the @sap/vscode-cds extension
CDS language support for VS Code and Business Application Studio
SAP CDS language support for IntelliJ IDEA
Interactive generator for CAP event handler files
Writer module for changing a CAP project's configuration from code
There is nothing to run: it is published for a generator or a script to call, not for a developer to invoke in a project, and it declares Node.js 22 or later.
Shared functions and types of the Fiori generators
Command line client and development toolkit for CAP
ESLint rules for projects the Fiori tools generators produce
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.
CLI of CAP development tools for Cloud Foundry workflows
There is no repository and no README: what the eight commands do is only readable from the compiled dist that ships in the package. Three of them — npmrc, install, project — are written for "SimpleMDG" projects rather than for CAP generally, so the reusable part is bind-local, run-local and debug. Seven releases up to July 2026. Its binding step writes the resolved VCAP_SERVICES into default-env.json in the project, where [@sap/cds-dk](artifact:sap-cds-dk) keeps only the place the credentials can be fetched from, so a project using it needs that file kept out of version control.
CAP Node.js runtime
Command line client and development toolkit for CAP
Dev-time wrapper for the SAP Application Router
Showcase for dev-approuter in front of two UI5 apps
Development container definition for CAP Node.js
Command line client and development toolkit for CAP
Command line client and development toolkit for CAP
Sample CAP plugin extending @sap/cds/common with reuse data
Sample CAP reuse service for orders, with a Fiori UI
Not in production. SAP states it is just a sample, not optimised for performance or security.
CAP Node.js runtime
Test support for CAP Node.js: server start, HTTP client, assertions
Fiori Elements mock server plugin taking a CDS file as metadata
Generates TypeScript types from a CDS model
Type definitions for the CAP Node.js SDK
API documentation extracted from SAP-published npm packages