Everything in CAP
Type: 2
Domain
Origin
Signals: Last 12 months
More
Group by: Capability
Distributed through
Form
CDS plugin adding embedded analytics to CAP for SAP Analytics Cloud
Not in a project on CAP 7 or earlier: the package declares `@sap/cds` >=8 and `@sap/cds-compiler` >=5 as peer dependencies.
Captures CAP service errors, deduplicates them and mails alerts
Alerting by mail is not telemetry — if you need traces and metrics correlated across handlers, that is a different layer. It also publishes no repository, so the package is the only thing to read.
GraphQL protocol adapter generated from the CDS model
Exports AsyncAPI documents for a CAP service's events
Generates Open Resource Discovery documents from a CAP model
Exposes a CAP service as OData V2
CAP plugin serving the Cardano blockchain as OData V4
CAP plugin indexing the Midnight blockchain, exposed as OData V4
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Calling an unbound CAP Java function from freestyle UI5
Neither the package manifest nor the repository tree declares a licence.
CAP Node.js server behind the OData Deep Dive tutorials
Generates OpenAPI documents from a CDS service
Swagger UI for a CAP service's OpenAPI definition
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.
Generates an MCP server from annotated CDS entities and actions
MCP server inside a CAP application with model and query tools
MCP server generated from a CDS model, forked from @gavdi/cap-mcp
Not published to npm. Install from source.
CAP travel-booking app built on xflights master data
WebSocket and Socket.IO adapter for CDS services
WebSocket push from a CAP service
Neither the package manifest nor the repository tree declares a licence.
Local chat client for SAP questions with a CAP LangGraph backend
Neither the package manifest nor the repository tree declares a licence.
sflight example extended with hierarchy support
Neither the package manifest nor the repository tree declares a licence.
CAP Node.js attachments with database, S3, Azure or GCP storage
CAP attachments stored in an SAP Document Management repository
If document versions are required, [@cap-js/sdm](artifact:cap-js-sdm) excludes versioned repositories in its [documented restrictions](https://raw.githubusercontent.com/cap-js/sdm/ad13b61f21816ebead2d08264a74521cfb75846c/README.md).
CAP Node.js attachments plugin with database or cloud storage
Fiori Elements page embedding upload controls on @cap-js/attachments
Neither the package manifest nor the repository tree declares a licence.
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.
Data federation for CAP via delegation, caching and replication
Collaborative draft support for CAP Node.js services
The maintainer marks this under active development; public APIs, annotation names and OData contracts may still change.
Data federation for CAP via delegation, caching and replication
Scheduled READ, MAP, WRITE pipelines between CAP services
CAP-to-CAP data federation over SAP HANA synonyms
When your adoption policy excludes experimental dependencies: the [maintainer’s README](https://github.com/cap-js/cds-federation-synonyms#about-this-project) explicitly labels this plugin experimental.
Replication between systems with CAP
Neither the package manifest nor the repository tree declares a licence.
reCAP 2026 workshop on data federation between CAP applications
User details and quickview links for createdBy and modifiedBy
Fills a CDS element from a database-backed number range
CAP's getting-started bookshop sample
Five-part workshop on CDS, from a first service to constraints
CAP data model of many-to-many relationships on a Star Wars dataset
CAP reuse package serving Airlines, Airports and Flights data
CAP Java reuse package for Airlines, Airports and Flights data
SAP HANA database service for CAP
PostgreSQL database service for CAP
SQLite database service for CAP, in memory during development
CAP plugin casting read values back to CDS model types
Tunnels CAP Node.js to a private PostgreSQL via Cloud Connector
CAP database adapter for Snowflake with OData V4 support
The maintainer marks this early development; expect the contract to move.
MongoDB as a CAP database service through Mongoose
It declares no peer range on [@sap/cds](artifact:sap-cds) and publishes no repository, so there is nothing to read but the package itself and no CI to look at.
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
CAP and Fiori app showing BTP Application Vulnerability Report data
Neither the package manifest nor the repository tree declares a licence.
CAP services reading each other's HANA tables across HDI containers
Neither the package manifest nor the repository tree declares a licence.
Composite CAP app from separately deployed services
CodeJam building a full-stack CAP app on SAP HANA Cloud
Spreadsheet upload into a CDS entity, parsed on the server
CAP Risks and Mitigations project with a Spreadsheet Upload button
Annotation-driven geocoding, address correction and routing for CAP
Nothing about it is readable from outside the package: there is no repository, no issue tracker, and the npm page carries no readme, so the README, the examples and the changelog can be read only from the tarball or a CDN mirror, and a bug has nowhere to be filed. Provider URLs are called from the plugin with API keys taken from environment variables in a .env file, so on BTP no call resolves through a destination and the keys live in the environment. The npm line stops at 1.0.1 on 3 November 2025; the changelog shipped inside that version is headed v2.1, so the version npm shows and the version the author counts are not the same.
CAP-to-CAP data federation over SAP HANA synonyms
When your adoption policy excludes experimental dependencies: the [maintainer’s README](https://github.com/cap-js/cds-federation-synonyms#about-this-project) explicitly labels this plugin experimental.
CAP services reading each other's HANA tables across HDI containers
Neither the package manifest nor the repository tree declares a licence.
CDS annotation vocabulary for entity search with schema discovery
The metadata is inconsistent: the declared repository is github.com/acme/search-vocab and the README installs @acme/search-vocab, neither of which matches the published name. One release, November 2025.
CAP Java plugin for soft delete with a softdelete aspect
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The Maven coordinate its README gives, io.github.miyasuta:cds-feature-softdelete:1.0.0, does not resolve on Maven Central as of 2026-09-07 — you build and install it from source.
CAP plugin turning DELETE into a flag on annotated entities
It changes what DELETE means for every client of the annotated projection, so anything that must actually remove a row — an erasure request, a retention job — has to go around it.
CAP plugin stripping whitespace from strings on write via @cds.trim
CAP plugin uppercasing strings on write via @cds.uppercase
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.
CAP plugin watching Cardano addresses and emitting events
App-to-app setups between CAP Java and CAP Node.js under AMS and IAS
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.
CodeJam on consuming external services from a CAP project
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
Event-driven RAG app with CAP, Cloud Integration and SAP HANA Cloud
Neither the package manifest nor the repository tree declares a licence.
CAP sample of SAP Event Mesh events feeding a multi-tenant SaaS app
CAP consumer of SAP Cloud Application Event Hub events
Business notifications from CAP to SAP Build WorkZone
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.
Calling ABAP function modules over RFC from a CAP service
Neither the package manifest nor the repository tree declares a licence.
CAP services reading each other's HANA tables across HDI containers
Neither the package manifest nor the repository tree declares a licence.
Composite CAP app from separately deployed services
CAP travel-booking app built on xflights master data
Data federation for CAP via delegation, caching and replication
CAP service actions calling OpenAI chat completions two ways
Neither the package manifest nor the repository tree declares a licence.
CAP reuse package serving Airlines, Airports and Flights data
CAP travel-booking app built on xflights master data
CAP service kind putting eleven model providers behind one API
Financial Risk Analyzer built by an agent grounded in SAP MCP servers
CDS plugin for building agents inside a CAP service
Not as a gateway or proxy for SAP Application APIs: capire's guide states that CAP-level agents are intended only for exposing custom CAP application services and are not an SAP-endorsed architecture or pathway for agentic access to those APIs, and sends the reader to the SAP Architecture Center for the endorsed routes. Not as the screen a user of the application talks to, either — the chat preview in the generic index.html page is marked experimental and for local development.
LangGraph Store keeping agent memory as CDS entities
LangGraph checkpointer backed by CDS for CAP agents
CAP service kind putting eleven model providers behind one API
Exposes an annotated CDS service as an Agent-to-Agent agent
No public repository is declared on the package, so the README is the documentation.
UI5 web interface for an agent built in a CAP service
Not where the agent is reached over anything other than A2A: the README states the plugin does not speak anything other than A2A as @cap-js/agents serves it. Not where an upgrade has to be uneventful either — it pins @cap-js/agents to exactly 0.9.1, calls that package pre-1.0 and days old at the time of writing, and says this plugin inherits that instability and to expect breakage on upgrade.
Worked example of the cap-agent-ui5-webui plugin
Neither the package manifest nor the repository tree declares a licence.
Local chat client for SAP questions with a CAP LangGraph backend
Neither the package manifest nor the repository tree declares a licence.
A2A reference letting Joule delegate to a CAP pro-code agent
CAP travel-booking app built on xflights master data
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 app validating invoices with Document Information Extraction
Value-help recommendations and SAP AI Core as a CAP service
Protocol adapter serving CAP data as TOON instead of JSON
CAP service kind putting eleven model providers behind one API
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.
Worked example of the cap-agent-ui5-webui plugin
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.
Local chat client for SAP questions with a CAP LangGraph backend
Neither the package manifest nor the repository tree declares a licence.
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 reference app for GenAI email support with RAG on HANA Cloud
Financial Risk Analyzer built by an agent grounded in SAP MCP servers
CodeJam on a CAP job posting service using SAP AI Core over OData
Product-review screen consuming ui5-cap-ai-features on CAP
Neither the package manifest nor the repository tree declares a licence.
CAP service kind putting eleven model providers behind one API
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.
Value-help recommendations and SAP AI Core as a CAP service
CAP service kind putting eleven model providers behind one API
Vector storage and similarity search on SAP HANA from CAP
Event-driven RAG app with CAP, Cloud Integration and SAP HANA Cloud
Neither the package manifest nor the repository tree declares a licence.
VECTOR_EMBEDDING in a CDS entity for FAQ similarity search
Neither the package manifest nor the repository tree declares a licence.
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 reference app for GenAI email support with RAG on HANA Cloud
CAP sample for semantic search with Generative AI Hub and HANA Cloud
Exposes an annotated CDS service as an Agent-to-Agent agent
No public repository is declared on the package, so the README is the documentation.
CAP integration with the SAP Audit Log service
OWASP Top 10 workshop exploiting and fixing flaws in a CAP Node.js app
TechEd 2025 workshop on OWASP Top 10 risks in CAP applications
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.
App-to-app setups between CAP Java and CAP Node.js under AMS and IAS
Neither the package manifest nor the repository tree declares a licence.
Authenticating a CAP service against Azure AD B2C
Authorization from DCL policies for Node.js apps on SAP Cloud Identity
CAP bookshop wired to the Authorization Management Service
Neither the package manifest nor the repository tree declares a licence.
CAP microservice on XSUAA managing users and authorizations
App-to-app setups between CAP Java and CAP Node.js under AMS and IAS
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.
OWASP Top 10 workshop exploiting and fixing flaws in a CAP Node.js app
CAP-based PWA for EV drivers proxying SAP E-Mobility OData APIs
TechEd 2025 workshop on OWASP Top 10 risks in CAP applications
Change history for annotated CAP entities
CAP integration with SAP Data Privacy Integration
Custom messages and handler classes for CAP input validation
Which CAP paths trigger @assert.target and which do not
Neither the package manifest nor the repository tree declares a licence.
reCAP 2025 workshop on cutting a CAP app into microservices
Companion repo deploying a CAP app to Cloud Foundry two ways
CAP sample sharing one domain model and database across apps
Not in production. SAP states it is just a sample, not optimised for performance or security.
CAP Java sample sharing one domain model across several apps
Not in production. SAP states it is just a sample, not optimised for performance or security.
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.