Everything in the atlas
Type
Domain: 3
Origin
Signals
More: CAP
Group by: Capability
CAP Node.js runtime
Fiori overview page comparing aggregated and plain donut-chart cards
Neither the package manifest nor the repository tree declares a licence.
Analytical List Page over a CAP OData V4 service
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 runtime
CAP Node.js attachments plugin with Object Store and malware scanning
CAP Node.js attachments plugin with database or cloud storage
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 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 Node.js plugin mapping CDS entities to SAP Document Management
Archived The declared repository is archived.
Functional boundary For versioned or thumbnail-enabled repositories, or bulk upload and download, the [README](https://raw.githubusercontent.com/vneecious/sap-cap-sdm-plugin/d9f036b16542e5c5b9b6dc704e0ba5f880193212/README.md) labels this an “early release” and lists those features as unsupported.
Fiori Elements page embedding upload controls on @cap-js/attachments
Neither the package manifest nor the repository tree declares a licence.
Media handling in core CDS with a UI5 UploadSet
Neither the package manifest nor the repository tree declares a licence.
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.
CAP Node.js runtime
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
CAP Node.js runtime
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.
Maven bill of materials pinning CAP Java module versions
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.
CAP Node.js runtime
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
CAP Node.js runtime
ISO content for CAP's countries, languages, currencies and timezones
Compiler from CDS models to CSN, EDMX and database schemas
User details and quickview links for createdBy and modifiedBy
Fills a CDS element from a database-backed number range
Maven bill of materials pinning CAP Java module versions
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
Base service shared by CAP's SQLite, PostgreSQL and HANA services
SAP HANA database service for CAP
PostgreSQL database service for CAP
SQLite database service for CAP, in memory during development
CLI for DROP and RENAME schema changes beside @cap-js/postgres
CAP plugin casting read values back to CDS model types
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 Node.js runtime
Database adapter for SAP HANA in CAP
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.
MySQL and MariaDB database adapter for CAP
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.
SAP HANA Cloud datasource for CAP Java applications
JDBC runtime for H2 and SQLite in CAP Java
PostgreSQL datasource for CAP Java applications
Maven bill of materials pinning CAP Java module versions
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
CAP beershop on PostgreSQL, predating an official adapter
CAP service reading and writing MongoDB from custom handlers
Neither the package manifest nor the repository tree declares a licence.
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 Node.js runtime
Command line client and development toolkit for CAP
Node.js deployer for SAP HANA Deployment Infrastructure containers
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.
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.
Fork of cds-dbm with deploy, load, diff and drop tasks
Release and repository quiet for 39 months.
CAP Node.js runtime
Multitenancy, tenant provisioning and extensibility for CAP
Node.js deployer for SAP HANA Deployment Infrastructure containers
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.
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 Node.js runtime
Maven bill of materials pinning CAP Java module versions
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 Node.js runtime
CAP Node.js runtime
Maven bill of materials pinning CAP Java module versions
CAP plugin stripping whitespace from strings on write via @cds.trim
CAP plugin uppercasing strings on write via @cds.uppercase
MCP server for CAP development: model and docs search
The tools are documented as meant for AI models and not a stable API, so anything built to parse `cds-mcp` output rather than to feed a model can break between releases. Its corpus is the CAP documentation, so Fiori elements, BTP service or ABAP questions are not in what `search_docs` indexes.
MCP server scaffolding CAP and CDS checked by cds compile
MCP server generating tools from a CAP or OData V4 service's metadata
CAP service kind putting eleven model providers behind one API
Agent skills for CAP development, each a SKILL.md with references
Collection of 41 agent skills, 37 for SAP development tasks
SAP's capire/skills packaged for the pi coding agent
If your tool reads the open skill standard directly, install [capire/skills](artifact:capire-skills) and skip the wrapper.
CAP review skill for coding agents with gates and prohibitions
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary There is no licence, so there is no grant to use or redistribute it. Everything else is secondary to that. Note too that its 'verified' claim means the skill text was checked against itself by an evaluation suite — not that the advice was run against a CAP version.
Agent skill for CAP multitenancy scaffolding
Local scaffolding only. Its own Out of Scope list names deployment to Cloud Foundry or Kyma, XSUAA and IAS configuration or any other BTP service binding, the SaaS Registry and subscription flow to real tenants, and automatic migration from the legacy `@sap/cds-mtx`. For the concepts rather than the scaffolding step, the README points at the `multitenancy` skill in [skillOverflow](artifact:dankromp-skilloverflow) by [Daniel Krompaß](actor:dankromp), which covers the MTX sidecar, `xs-security.json`, tenant lifecycle hooks and the deployment path and runs no commands at all.
Agent skills for CAP development, each a SKILL.md with references
Collection of 41 agent skills, 37 for SAP development tasks
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
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 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.
Toolkit turning a CAP service into tools for agent frameworks
A2A adapter turning a CAP Java service into an LLM-backed agent
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
Orchestration Service client for templating, grounding and masking
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.
Orchestration Service client for templating, grounding and masking
Generative AI in CAP with fields anonymised through SAP HANA
Not where the records sit anywhere but [SAP HANA Cloud](artifact:btp-hana-cloud): the similarity search and the single retrieval method are both written against its vector engine, and the embeddings and the chat call go through [SAP AI Core](artifact:btp-ai-core), so a project without both has nothing here to call. Not where the dependency has to be an SAP-supported one either: the README states that the plugin is not an official SAP product and is published as a community contribution.
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
Vercel AI SDK provider for SAP AI Core
AI Core control plane API surface of SAP's AI SDK
Shared internals of SAP's AI SDK
Client for foundation models via SAP AI Core and Generative AI Hub
Orchestration Service client for templating, grounding and masking
Client for prompts kept in SAP's prompt registry
CAP service kind putting eleven model providers behind one API
MCP server answering plain-English questions against a CDS schema
Bridge from CAP Java to SAP AI Core, with Fiori field recommendations
Generative AI in CAP with fields anonymised through SAP HANA
Not where the records sit anywhere but [SAP HANA Cloud](artifact:btp-hana-cloud): the similarity search and the single retrieval method are both written against its vector engine, and the embeddings and the chat call go through [SAP AI Core](artifact:btp-ai-core), so a project without both has nothing here to call. Not where the dependency has to be an SAP-supported one either: the README states that the plugin is not an official SAP product and is published as a community contribution.
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.
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.
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.
Orchestration Service client for templating, grounding and masking
Client for prompts kept in SAP's prompt registry
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.