Everything in the atlas
Type
Domain
Origin
Signals: 2
More: CAP
Group by: Capability
ESLint plugin with one consultancy's rules for CDS files
Neither the package manifest nor the repository tree declares a licence.
Shared ESLint configuration for SAPUI5 and CAP projects
ESLint rules for projects the Fiori tools generators produce
SAP's ESLint plugin for CDS
ESLint rules flagging deprecated CAP configuration
Regex naming rules for SAP HANA artifacts in a CAP project
Everything it checks is a name: a file name under `rootDir`, or an identifier a parser extracted from a file, so a convention that cannot be written as a regex over one name has no rule shape here. Content rules targeting `.hdbanalyticalprivilege` or `.hdbconstraint` return no results, which the README states as not yet implemented, so conventions centred on those two artifact types go unchecked.
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 starting several CAP services and an AppRouter locally together
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.
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
Command line client and development toolkit for CAP
Dev-time wrapper for the SAP Application Router
Serves a Vite app through cds watch and imports .cds files
Showcase for dev-approuter in front of two UI5 apps
Ten short CAP Java references, one document per topic
Development container definition for CAP Node.js
CAP project simulating S/4HANA Private Edition OData APIs locally
reCAP 2025 workshop on CAP's local-development toolset
Eight-exercise tour of CAP features, from mocking to plugins
Command line client and development toolkit for CAP
Command line client and development toolkit for CAP
Sample CAP plugin adding a generic data browser
Its own readme carries a caution: this is a sample, not intended for production use. It exists to demonstrate the plugin mechanism, and the bookstore sample is where it is used.
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.
Sample CAP Java reuse service for orders, with a Fiori UI
Not in production. SAP states it is just a sample, not optimised for performance or security.
Sample CAP reuse service for reviews, with a Fiori UI
Not in production. SAP states it is just a sample, not optimised for performance or security.
Sample CAP Java reuse service for reviews, with a Vue UI
Not in production. SAP states it is just a sample, not optimised for performance or security.
Eight-exercise tour of CAP features, from mocking to plugins
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.
Compares a CAP project's CSV data with its database rows
CAP Node.js runtime
ISO content for CAP's countries, languages, currencies and timezones
Fills db/data with relationally consistent CSV from a .cds schema
Test support for CAP Node.js: server start, HTTP client, assertions
Fiori Elements mock server plugin taking a CDS file as metadata
Gherkin scenarios driving a running CAP service
Sandbox launchpad for all SAPUI5 apps in a CAP workspace
Terminal UI running Bruno collections against a CAP service
Ten short CAP Java references, one document per topic
CAP bookshop with wdi5 system tests for a CI/CD tutorial
Decorator-driven handler registration for CAP in TypeScript
Typed BaseRepository over CAP entities
Convention-based handler layer for CAP with draft lifecycle hooks
CDS build task compiling TypeScript sources during cds build
CLI generating TypeScript interfaces from a CDS model
Generates TypeScript types from a CDS model
Type definitions for the CAP Node.js SDK
Minimal CAP project in TypeScript
Neither the package manifest nor the repository tree declares a licence.
API documentation extracted from SAP-published npm packages
CAP Node.js runtime
Fiori draft handling and UI-facing behaviour for CAP services
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.
Convention-based handler layer for CAP with draft lifecycle hooks
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
CAP Java draft cancel on composition items as a flag update
Neither the package manifest nor the repository tree declares a licence.
List report inline edit on a draft-enabled CAP service
Neither the package manifest nor the repository tree declares a licence.
Event registration app showing OData V4 draft with UI5 and CAP
Parser for annotations in CDS source
Converter from CDS annotations to their OData form
Programmatic API for reading and writing project annotations
CAP Node.js runtime
Fiori draft handling and UI-facing behaviour for CAP services
Entry point for generating a Fiori application from a template
Wrapper around the CDS compiler for annotation handling
OData annotation features for the @sap/vscode-cds extension
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.
User details and quickview links for createdBy and modifiedBy
Singleton entity whose flags drive Fiori elements feature control
Incident Management reference application for CAP
One object page field made read-only from another's value, two ways
Neither the package manifest nor the repository tree declares a licence.
List report inline edit on a draft-enabled CAP service
Neither the package manifest nor the repository tree declares a licence.
Outbound navigation patterns from a Fiori Elements list report
Neither the package manifest nor the repository tree declares a licence.
Travel-booking reference app on CAP Node.js and Java backends
Showcase of Fiori elements for OData V4 features on a CAP backend
CodeJam building a bookshop app on the flexible programming model
Exercise solutions for the UX405 course on Fiori elements with CAP
CLI for the SAP BTP Application Frontend service
CAP Node.js runtime
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.
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.
CAP bookshop showing UI5 development with cds-plugin-ui5
CAP Node.js runtime
CAP plugin rendering UI5 views with entity data on the server
On the UI5 path what comes back is an XML view or fragment with the data already substituted, streamed as the entity's media content, rather than an HTML page — the README calls this pre-rendering, and only the Vue path produces markup. The view kept under `srv/` has its UI5 bindings replaced by Handlebars expressions, so it is a second copy of the view, separate from the one the application ships. Version 1.0.8 declares `@sap/cds` `>=8` as its peer dependency, which puts a project on CAP 7 outside its stated range.
CAP Node.js runtime
Triggers n8n workflows from a CAP application
Starts and manages SAP Build Process Automation processes from CAP
Integration of CAP with n8n workflows and triggers
Triggers n8n workflows from CAP Java through the outbox
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.
Fiori documentation indexed as embeddings
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.
Sources of capire, the CAP documentation
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Java implementation of the capire/bookshop getting-started sample
Java implementation of the capire/bookstore composite app
CAP's getting-started bookshop sample
Composite CAP app from separately deployed services
Incident Management reference application for CAP
CAP reference app for lightweight local inventory management
Incident Management CAP app for the SAP BTP Developer's Guide
Financial Risk Analyzer built by an agent grounded in SAP MCP servers
Travel-booking reference app on CAP Node.js and Java backends
Bookshop app demonstrating the CAP Java SDK end to end
CAP-based PWA for EV drivers proxying SAP E-Mobility OData APIs
Event registration app showing OData V4 draft with UI5 and CAP
CAP reference app validating Ariba supplier registration data
CAP reference application for tail spend management
Todo app with CAP and SAPUI5 in TypeScript over OData V4
Neither the package manifest nor the repository tree declares a licence.
CAP travel-booking app built on xflights master data
CAP Java travel-booking app built on xflights-java master data
Monorepo of CAP's SQL database services
LangGraph agent and UI5 chat screen over four BTP MCP servers
Neither the package manifest nor the repository tree declares a licence.
CAP agent writing reports into a shared SDM document workspace
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.