Everything in the atlas
Type
Domain
Origin
Signals
More: 2
Group by: Type
Report pushing ABAP objects to SAP Translation Hub and back
No published releases; repository quiet for 43 months.
Software-engineering metrics for an ABAP class or package
No published releases; repository quiet for 43 months.
Fiori launchpad notification for application log errors
In-system search tool for CDS views
No published releases; repository quiet for 29 months.
UI5 app for OData test requests and ABAP Push Channels
Python agent alerting on SAP AI Core capacity unit consumption
Generates TypeScript types from a CDS model
Compiler from a CDS service to SEGW model and data provider classes
The generated files are copied or deployed into the ABAP system by hand, the fourth step of its own usage list, so nothing keeps an activated service in step with the model it was generated from. Its peer dependency is `@sap/cds` ^9.8, so it does not install into a project on an earlier CAP release.
ESLint rules for projects the Fiori tools generators produce
UI5 CLI middleware for Istanbul code coverage
Deprecated UI5 Tooling extensions for UI5 Web Components wrappers
The declared repository is archived.
Windows build packaging Eclipse with ADT as a portable IDE
GitHub Action setting up the Cloud Foundry CLI
Dev-time wrapper for the SAP Application Router
UI5 CLI middleware proxying the dev server through @sap/approuter
UI5 CLI middleware running a CDS server inside the UI5 dev server
Experimental UI5 middleware for hot module replacement
UI5 middleware syncing interactions across browsers over websocket
UI5 middleware serving a chosen welcome page at the root path
Live reload middleware for the UI5 dev server
UI5 middleware recording OData traffic as mock server datasets
It records what the app actually asked for, so an entity no recorded journey touched is not in the dataset and replay will not answer for it. Its own README asks for `fiori-tools-appreload` to be disabled while recording, because a reload loop is what happens otherwise.
UI5 dev server middleware adding an OpenID Connect login
UI5 middleware logging in with Playwright and reusing the session
UI5 middleware serving a locally built UI5 framework
UI5 middleware serving static resources from a path or npm package
Dev-server middleware proxying requests to a backend system
UI5 middleware including one UI5 application in another
UI5 middleware serving static resources from JAR files (WebJars)
WebSocket support for Express-based dev servers such as UI5's
UI5 Tooling task writing the service name into the importer manifest
UI5 builder task cachebusting standalone UI5 applications
UI5 builder task appending copyright headers to source files
UI5 builder task flattening library output for SAP NetWeaver
UI5 builder task checking XML views for missing i18n texts
UI5 builder task minifying XML views and fragments
UI5 builder task turning a UI5 app into a progressive web app
UI5 Tooling task transpiling TypeScript and ES modules
Build task packaging the UI5 build result as a zip archive
UI5 CLI extension compiling Less files into CSS
UI5 tooling extensions loading npm packages as UI5 modules
UI5 CLI extension for string replacement during the build
UI5 CLI extension transpiling code during the UI5 build
Business-level metrics from CDS annotations via @cap-js/telemetry
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.
Exposes a CAP service as OData V2
WebSocket and Socket.IO adapter for CDS services
CAP integration with SAP Integration Suite advanced event mesh
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.
Value-help recommendations and SAP AI Core as a CAP service
Exports AsyncAPI documents for a CAP service's events
CAP Node.js attachments with database, S3, Azure or GCP storage
CAP integration with the SAP Audit Log service
Change history for annotated CAP entities
Connects a running CAP application to the CAP console
Inspects database entities and contents at CAP service level
CAP integration with SAP Data Privacy Integration
Consumes events from SAP Cloud Application Event Hub in CAP
GraphQL protocol adapter generated from the CDS model
SAP HANA database service for 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
Business notifications from CAP to SAP Build WorkZone
Generates OpenAPI documents from a CDS service
Generates Open Resource Discovery documents from a CAP model
PostgreSQL database service for CAP
Prints documents held in CAP entities through SAP Print service
Starts and manages SAP Build Process Automation processes from CAP
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).
SQLite database service for CAP, in memory during development
OpenTelemetry instrumentation for CAP services
Renamed copy of @cap-js/notifications under another scope
Release and repository quiet for 24 months.
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.
Generates an MCP server from annotated CDS entities and actions
CAP plugin generating value help for enum fields from an annotation
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 serving the Cardano blockchain as OData V4
CAP plugin indexing the Midnight blockchain, exposed as OData V4
CAP plugin watching Cardano addresses and emitting events
CAP service kind putting eleven model providers behind one API
Vector storage and similarity search on SAP HANA from CAP
CAP Node.js attachments plugin with Object Store and malware scanning
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.
CAP Node.js attachments plugin with database or cloud storage
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.
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.
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.
MCP server generated from a CDS model, forked from @gavdi/cap-mcp
Not published to npm. Install from source.
Integration of CAP with n8n workflows and triggers
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.
UI5 frontend performance and error capture for CAP
Custom messages and handler classes for CAP input validation
JWT authentication for CAP without xsuaa or xssec
Last released April 2022 at 0.0.2, and no repository is declared on the package.
Gherkin scenarios driving a running CAP service
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.
Feature-toggle pattern for CAP CDS
Last released June 2022 at 0.0.6, and no repository is declared on the package.
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.
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.
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.
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.
OpenTelemetry support for the CDS Node.js runtime
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.
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.
Compares a CAP project's CSV data with its database rows
CLI for operating tenants of multitenant CAP applications
Command line for changing features of an existing Fiori project
UI5 Tooling command line for project setup, dev server and build
Static analysis tool for UI5 projects
Containerised script setting up an SAP BTP account from JSON config
The declared repository is archived.
AWK script sketching an ER diagram from .cds files
No published releases; repository quiet for 26 months.
Developer-centric command line for SAP HANA
CLI adding SAP developer knowledge and MCP servers to AI coding tools
UI5 Tooling module deploying Fiori/UI5 apps to SAP systems
Command-line linter for UI5 classes, XML views and i18n files
Two of its JavaScript and TypeScript checks, EventTypeLinter and WrongNamespaceLinter, apply to TypeScript projects only.
Java Swing tool maintaining Partner Directory entries for the Pipeline
Local desktop workspace for AI conversations with SAP connectors
Machine-readable catalogue of SAP BTP pay-as-you-go services
Sources of capire, the CAP documentation
ABAP syntax cheat sheets with executable demo classes
Guides connecting hyperscaler sources into SAP Datasphere in BDC
Source repository of SAP's reference architectures
Generates Helm charts for the CAP Operator on Kubernetes
Yeoman generator for Cloud Connector mappings and BTP destinations
cds add plugin adding the incidents-app model to a project
npm-init wrapper for the Easy-UI5 Yeoman generator
npm initializer adding wdi5 testing to an existing UI5 app
Yeoman meta-generator for scaffolding UI5 projects
Yeoman generator for UI5 tooling-extension projects
Release and repository quiet for 33 months.
Easy-UI5 generator scaffolding a new UI5 application
Easy-UI5 generator scaffolding a Fiori Launchpad plugin
Easy-UI5 generator scaffolding a new UI5 library
Yeoman generator for UI5 libraries wrapping UI5 Web Components
No published releases; repository quiet for 35 months.
Yeoman generator for UI5 projects holding several applications
Not for a single-application project with no deployment configuration: for that the README points to [generator-ui5-app](artifact:ui5-community-generator-ui5-app) instead.
Yeoman generator for a UI5 app that loads a React app
Quiet Release and repository quiet for 38 months.
Functional boundary The scaffold is JavaScript and not TypeScript, and `react-router-dom` and UI5 Web Components are not included; its README leaves both for the project to add.
Easy-UI5 generator scaffolding a TypeScript UI5 application
Generator for a TypeScript UI5 FlexibleColumnLayout app on OData
Easy-UI5 generator for a TypeScript Fiori launchpad plugin
Easy-UI5 generator scaffolding a TypeScript UI5 library
Yeoman generator scaffolding wdi5 test configuration into a UI5 app
No published releases; repository quiet for 27 months.
Generator of ABAP type definitions from JSON structures
Command line generator of UI5 custom controls from html
Release and repository quiet for 29 months.
Chrome extension generating OPA5 or wdi5 tests from recorded journeys