Everything in the atlas
Type
Domain: 2
Origin
Signals
Content
More
Group by: Ecosystem
Compares a CAP project's CSV data with its database rows
Interactive generator for CAP event handler files
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.
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
Connects a running CAP application to the CAP console
Inspects database entities and contents at CAP service level
Placeholder package under a CAP annotations name, no annotations
The manifest calls it a dummy library exposing custom CDS annotations, but the published contents are a one-line README, a single exported barrier() whose body is throw Error("not yet implemented"), and no .cds file at all — there is nothing to import and nothing to annotate with. No repository, one release, May 2025.
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
Decorator-driven handler registration for CAP in TypeScript
Typed BaseRepository over CAP entities
Interactive project installer for CAP Node.js
CAP plugin generating value help for enum fields from an annotation
CLI starting several CAP services and an AppRouter locally together
CAP plugin putting a draft-capable facade in front of imported OData
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.
Writer module for changing a CAP project's configuration from code
There is nothing to run: it is published for a generator or a script to call, not for a developer to invoke in a project, and it declares Node.js 22 or later.
Parser for annotations in CDS source
Converter from CDS annotations to their OData form
ESLint rules for projects the Fiori tools generators produce
Fiori Elements mock server plugin taking a CDS file as metadata
Programmatic API for reading and writing project annotations
Shared functions and types of the Fiori generators
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.
CLI for the SAP BTP Application Frontend service
CAP Node.js runtime
ISO content for CAP's countries, languages, currencies and timezones
Command line client and development toolkit for CAP
Fiori draft handling and UI-facing behaviour for CAP services
Language server for CDS
SAP's ESLint plugin for CDS
CAP project generator behind SAP Business Application Studio's wizard
CDS project generator, deprecated in favour of @sap/cds-dk
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
CDS language support for VS Code and Business Application Studio
Endpoint discovery for CAP services deployed to Cloud Foundry
Workspace-wide CSN cache for querying CAP entities and columns
Static end-to-end tracer of one CAP operation across repositories
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.
Convention-based handler layer for CAP with draft lifecycle hooks
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.
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.
Fills db/data with relationally consistent CSV from a .cds schema
User details and quickview links for createdBy and modifiedBy
Gherkin scenarios driving a running CAP service
Eclipse plugin for the CDS language
Neither the package manifest nor the repository tree declares a licence.
Typed class-based service layer over CAP ApplicationService
Last released July 2022, and no repository is declared on the package.
SAP CDS language support for IntelliJ IDEA
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.
Sandbox launchpad for all SAPUI5 apps in a CAP workspace
One handler file per entity in CAP services
CDS build task compiling TypeScript sources during cds build
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.
Decorator-based routing of CAP service handlers in TypeScript
Release and repository quiet for 46 months.
TextMate grammar for the CDS language
Not an editor integration. If you want completion, navigation and diagnostics, that is the CDS language server, not this.
CLI generating TypeScript interfaces from a CDS model
GitHub Action setting up the Cloud Foundry CLI
Connects a running CAP Java app to CAP console for monitoring
Browser dashboard for a running CAP Java service during development
Maven plugin running CDS build steps in a CAP Java project
Maven archetype generating a new CAP Java project
Maven bill of materials pinning CAP Java module versions
Dev-time wrapper for the SAP Application Router
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.
Joule's generative AI inside SAP Build Code
Attaches a debugger to a CAP app running on Cloud Foundry
AWK script sketching an ER diagram from .cds files
No published releases; repository quiet for 26 months.
Terminal UI running Bruno collections against a CAP service
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.
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.
CDS vocabulary for User-Rendered Patterns display annotations
The declared repository is github.com/your-username/urp-vocab, an unedited placeholder. Three releases, September 2025.
Serves a Vite app through cds watch and imports .cds files
CDS language support for the Zed editor
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.
Showcase for dev-approuter in front of two UI5 apps
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.
Simple CDS bookshop model used across CAP explanations
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.
CAP service in TypeScript using types from @cap-js/cds-typer
Common.DefaultValuesFunction pointed at a CAP service function
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 draft cancel on composition items as a flag update
Neither the package manifest nor the repository tree declares a licence.
Maven parent pom pinning cds-services-bom and Spring Boot for CAP Java
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.
Ten short CAP Java references, one document per topic
CAP sample drawing a material BOM as a UI5 network graph
Neither the package manifest nor the repository tree declares a licence.
Development container definition for CAP Node.js
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.
Minimal CAP project in TypeScript
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.
Incident Management reference application for CAP
CAP bookshop showing UI5 development with cds-plugin-ui5
Sample CAP plugin extending @sap/cds/common with reuse data
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.
CAP and UI5 app for in-place table maintenance with SmartTable
Neither the package manifest nor the repository tree declares a licence.
CAP project simulating S/4HANA Private Edition OData APIs locally
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.
Repository template with LICENSE, REUSE and compliance files
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.
API documentation extracted from SAP-published npm packages
CAP bookshop with wdi5 system tests for a CI/CD tutorial
reCAP 2025 workshop on CAP's local-development toolset
Travel-booking reference app on CAP Node.js and Java backends
Eight-exercise tour of CAP features, from mocking to plugins
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
Event registration app showing OData V4 draft with UI5 and CAP
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.
UI5 apps calling CAP OData actions and functions from custom code
Neither the package manifest nor the repository tree declares a licence.
UI5 custom control that runs an abap2UI5 app inside a host app
The page and the [abap2UI5](artifact:abap2ui5-abap2ui5) service have to share an origin: an `endpoint` that resolves to another origin is refused, and abap2UI5 rejects a POST whose `Origin` names another host. A host that routes by the URL hash, such as a Fiori elements app or an app with a UI5 router, needs abap2UI5 1.146.0 or later, because 1.145.0 clears the host's hash after every roundtrip. One frontend per page: the first control that starts decides which endpoint the frontend comes from.
CLI translating UI5 i18n.properties files with OpenAI
UI5 custom control formatting dates with Day.js
No published releases; repository quiet for 52 months.
Framework core: module loader, MVC runtime, binding, routing, theming
Colour, font and metric definitions of the SAP themes
Command line for changing features of an existing Fiori project
Writer of flexible programming model elements into Fiori elements apps
Reader and writer for i18n bundles of UI5 or CAP projects
Writer that adds an OData service to an existing UI5 project
OASIS and SAP OData vocabularies with a VocabularyService
Writer of the base structure of a UI5 project from Node code
Rule-based checker for SAPUI5 and OpenUI5 projects
Not in a project whose dependencies must all carry an open-source licence: KAEV is proprietary software, its licence page states that downloading or viewing the npm package does not by itself grant permission to use, copy, modify, redistribute, sublicense, sell, host or create derivative works, and the LICENSE file shipped with the package carries the controlling terms. Not as the last word on whether a UI5 application is secure: its rule reference states that a heuristic finding is not proof of a vulnerability, and its documentation puts professional security review beside it rather than under it.
Plugin-based JSX runtime for UI5 views written as .tsx
Lowercase HTML tags such as `<div>` typecheck but throw: the default renderer constructs UI5 controls, and the HTML-aware renderer plugin is described as planned. `withScope` restores the previous scope on a synchronous return only, so an `await` inside its callback leaks the scope on runtimes without `AsyncLocalStorage`. A view that has to stay adaptable through UI5 flexibility has no path here yet: the project's [Devtoberfest session](content:devtoberfest-2026-ui5-views-type-safe-tsx) states that flexibility support is not built in yet.
Scaffolded UI5 TypeScript app consuming the JSX runtime
It shows the wiring and a converted view pair, not the runtime's API surface; the directives, the plugin SPI and the binding forms are demonstrated in [@ui5-community/jsx-runtime-showcase](artifact:ui5-community-jsx-runtime-showcase) instead.
Showcase and documentation app of @ui5-community/jsx-runtime
Its views are not a template for application code: every showcase view overrides `getController()` to return itself so a sample stays readable in one file, and the gotchas page says not to ship that in production, where a view keeps a separate `*.controller.ts`. Routing from a sample, an `ODataModel` v2 or v4, `sap.ui.mdc.Table`, forms and custom control authoring in TSX are absent by decision and documented as deferred.
UI5 Tooling command line for project setup, dev server and build
Static analysis tool for UI5 projects
Internal logger of the UI5 CLI
MCP server for UI5 development with ten tools
It reads a UI5 project and the framework's own documentation, not a running system or a backend: a question about the service behind the app is answered somewhere else. Node.js v20.17 or v22.9 and above.
UI5 CLI middleware for Istanbul code coverage
Deprecated UI5 Tooling extensions for UI5 Web Components wrappers
The declared repository is archived.
SAP's UI elements as standard custom elements
Not where the UI library itself is expected to bind data: the documentation leaves binding a component's content and events to the host framework. Not from a CDN script tag: the project publishes none, so it assumes a build step.
OpenUI5 sample app set up with the UI5 CLI