Everything in the atlas
Type
Domain
Origin
Signals: 2
More: 2
Group by: Ecosystem
Compares a CAP project's CSV data with its database rows
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
Exposes a CAP service as OData V2
SDK for SAP Advanced Financial Closing scheduling providers on CDS
CAP integration with SAP Integration Suite advanced event mesh
Value-help recommendations and SAP AI Core as a CAP service
Exports AsyncAPI documents for a CAP service's events
Generates Helm charts for the CAP Operator on Kubernetes
Test support for CAP Node.js: server start, HTTP client, assertions
Generates TypeScript types from a CDS model
Type definitions for the CAP Node.js SDK
Change history for annotated CAP entities
Connects a running CAP application to the CAP console
Inspects database entities and contents at CAP service level
Consumes events from SAP Cloud Application Event Hub in CAP
Exposes CAP services as MCP servers for AI agents
SAP prohibits gateway/proxy use for SAP Application APIs; the Atlas applies that prohibition to CAP wrappers around those APIs. Data changes require application-defined unbound actions, and the adapter supplies no rate limiting, agent-action audit logging, approval workflows or policy enforcement. In beta, with nine releases in the six weeks after the first, so pin it.
Triggers n8n workflows from a CAP application
Generates Open Resource Discovery documents from a CAP model
OpenTelemetry instrumentation for CAP services
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.
LangChain vector store on SAP AI Core Document Grounding
LangChain vector store with CDS entities for embeddings
LangGraph Store keeping agent memory as CDS entities
Deep Agents filesystem over an SAP Document Management repository
Not a way to edit Office formats: the author states that access to a file does not automatically provide native editing of Word documents, spreadsheets or PDFs, and suggests starting with text-based content such as instructions, templates and reports. Not a control point either: a prompt telling the agent to ask for confirmation or to leave a template alone needs enforceable application controls where that is a business requirement, and the host application stays responsible for the authenticated request context and tenant isolation.
LangGraph checkpointer backed by CDS for CAP agents
CAP plugin generating value help for enum fields from an annotation
MCP server inside a CAP application with model and query tools
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 casting read values back to CDS model types
CAP plugin stripping whitespace from strings on write via @cds.trim
CAP plugin uppercasing strings on write via @cds.uppercase
CAP plugin letting the REST adapter accept XML payloads
MCP server exposing the ODATANO Cardano-to-OData bridge as tools
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.
MCP server exposing the NIGHTGATE Midnight attestation layer
DB2 adapter for CDS
The README is one line and the package carries no licence field. Last released July 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 putting a draft-capable facade in front of imported OData
Authorization from DCL policies for Node.js apps on SAP Cloud Identity
CLI for the SAP BTP Application Frontend service
CAP Node.js runtime
Compiler from CDS models to CSN, EDMX and database schemas
Command line client and development toolkit for CAP
Multitenancy, tenant provisioning and extensibility for CAP
Wrapper around the CDS compiler for annotation handling
OData annotation features for the @sap/vscode-cds extension
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.
CAP service kind putting eleven model providers behind one API
Vector storage and similarity search on SAP HANA from CAP
MCP server answering plain-English questions against a CDS schema
Playback-only SAP Companion (Help4) workarea served from CAP
Not behind a managed approuter: SAP Build Work Zone does not expose the `/$companion/**` routes, so Companion never reaches CAP, and the README names managed approuter and Work Zone as out of scope for v1. Not where help has to be authored in a browser, since the editor, the producer and writes are absent and content lives in files the plugin compiles.
Bridge from CAP Java to SAP AI Core, with Fiori field recommendations
CSV seed data generated from @Mockdata annotations with Faker
Quiet Release and repository quiet for 27 months.
Functional boundary Not a test-data factory. It writes files at build time to seed a database, so it does not build fixtures inside a unit test. The declared peer range stops at cds 7 — nothing says it fails on 9, but nothing says it was tried either.
MCP server generating tools from a CAP or OData V4 service's metadata
Toolkit turning a CAP service into tools for agent frameworks
CAP caching plugin for query results and remote service responses
When user-dependent responses are cached without user-aware or explicit operation keys, or translated responses share keys across locales. These cases require key isolation; locale-aware keys are off by default.
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
Scheduled READ, MAP, WRITE pipelines between CAP services
Delta deployment and migrations for CAP database adapters
Archived The declared repository is archived.
Functional boundary The repository is archived, so nothing here will move again. Fine to keep where it already runs; anything new should start from what the current cds deploy leaves open rather than from this.
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
Feature-toggle pattern for CAP CDS
Last released June 2022 at 0.0.6, and no repository is declared on the package.
Typed class-based service layer over CAP ApplicationService
Last released July 2022, and no repository is declared on the package.
Reusable internals for authors of CAP extensions
Explicitly internal utilities, so the surface is not a stable public API and last moved in March 2024. 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.
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.
PostgreSQL adapter for SAP CDS from the SAP Mentors community
The declared repository is archived.
One handler file per entity in CAP services
UI5 CLI middlewares running inside the CDS server
For a deployed application's UI. The README adds it with `npm add cds-plugin-ui5 -D`, a development dependency of the CDS server, and states nothing about a build or a deployment.
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.
Destination resolution and axios calls from CAP configuration
Release and repository quiet for 46 months.
CAP Java plugin for SAP Integration Suite, advanced event mesh
CAP Java attachments with database storage and an Object Store module
For deployed environments, the [README](https://raw.githubusercontent.com/cap-java/cds-feature-attachments/302f61c8bb76a0f54f43482ad91d89bf7dc5540f/README.md) excludes the cds-feature-attachments-fs file-system target, which is intended only for local development and testing.
CAP Java plugin sending audit log events to SAP Audit Log service
Connects a running CAP Java app to CAP console for monitoring
Connects CAP Java messaging to SAP Cloud Application Event Hub
Triggers n8n workflows from CAP Java through the outbox
Business notifications from CAP Java via SAP Alert Notification
Generates Open Resource Discovery documents from a CAP Java model
CAP Java plugin for attachments in SAP Document Management
If document versions are required, the [documented restrictions](https://raw.githubusercontent.com/cap-java/sdm/673769f24ef66fd97daa6a6be41262d45065d3fe/README.md) exclude versioned repositories.
CAP plugin joining external entities with internal tables at query
The declared repository is on SAP's internal GitHub (github.tools.sap) and is not publicly reachable, so npm is the only place to read anything about it.
MCP server searching seventeen SAP documentation repositories
It reads documentation, never a system: nothing in it opens a package.json, a CDS model or an ABAP client, so a question about what your own project does has to be answered elsewhere. The offline half is only as fresh as the submodules the last build pinned, and the index answers where something is written down rather than which of two packages fits a task.
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 agent writing reports into a shared SDM document workspace
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.
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.
CDS plugin and UI5 controls for AI text features via SAP AI Core
It is text processing, not an agent: there is no tool calling, no retrieval and no conversation. It needs SAP AI Core, and the backend half needs [@sap-ai-sdk/orchestration](artifact:sap-ai-sdk-orchestration) installed alongside it — an optional peer, so a frontend-only install stays lean.
Demo CAP bookshop with server-rendered UI5 views
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary As a deployment template it stops at the service: the `mta.yaml` has one module, `gen/srv` on the Node.js buildpack, and no HTML5 repository or router module for the app.
Serves a Vite app through cds watch and imports .cds files
CAP services and a UI for trying role restrictions with mock users
Neither the package manifest nor the repository tree declares a licence.
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 bookshop with Fiori elements UI deployed whole to Cloud Foundry
Neither the package manifest nor the repository tree declares a licence.
Fiori overview page comparing aggregated and plain donut-chart cards
Neither the package manifest nor the repository tree declares a licence.
Java implementation of the capire/bookstore composite app
Worked example of the cap-agent-ui5-webui plugin
Neither the package manifest nor the repository tree declares a licence.
CAP service in TypeScript using types from @cap-js/cds-typer
Common.DefaultValuesFunction pointed at a CAP service function
CAP service computing embeddings with HANA Cloud vector_embedding
CAP service serving Northwind's external OData Products as its own
Mass edit enabled in a Fiori elements list report over CAP
Singleton entity whose flags drive Fiori elements feature control
CAP project built and deployed to Cloud Foundry by GitHub Actions
Consumer side of a CAP Java parent pom promotion model with Renovate
Neither the package manifest nor the repository tree declares a licence.
CAP Java service consuming a Business Partner API mocked in Node.js
Neither the package manifest nor the repository tree declares a licence.
CAP sample drawing a material BOM as a UI5 network graph
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.
Approuter session held in a bound Redis cache instance
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary Not a descriptor to deploy as it stands: the approuter's `sessionSecret` is written out in `mta.yaml`.
Fiori elements app in the HTML5 Application Repository with cdm.json
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The subaccount destination's url names the us10 trial's repository runtime, so another region or subaccount needs it rewritten before the descriptor deploys.
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
Chat app on CAP and SAPUI5 against the OpenAI API
It calls the OpenAI API directly with a key in the environment. It was written in early 2023 and last touched in May 2023, which is before SAP AI Core and the CAP LLM plugins existed — so read it for the shape of the application, not for how a CAP service should reach a model today.
CAP project simulating S/4HANA Private Edition OData APIs locally
CAP samples calling SAP AI Core through the SAP Cloud SDK for AI
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples comparing SAP AI Core responses with content filtering
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples generating email through SAP AI Core with anonymization
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples using SAP AI Core's Prompt Registry for templates
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples filling a prompt template sent to SAP AI Core
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples embedding CSV rows into the SAP HANA Cloud vector store
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples running RAG similarity queries over SAP HANA Cloud vectors
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP service reading and writing MongoDB from custom handlers
Neither the package manifest nor the repository tree declares a licence.
Product-review screen consuming ui5-cap-ai-features on CAP
Neither the package manifest nor the repository tree declares a licence.
UI5 apps calling CAP OData actions and functions from custom code
Neither the package manifest nor the repository tree declares a licence.