Everything in CAP
Type
Domain: 3
Origin
Signals
More
Group by: Capability
CAP integration with the SAP Audit Log service
CAP Java plugin sending audit log events to SAP Audit Log service
CAP Java handler for SAP Audit Log service API version 2
Maven bill of materials pinning CAP Java module versions
Ingests and retains compliance audit data from BTP
CAP Node.js runtime
Token validation and security context for XSUAA and IAS
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.
JWT authentication for CAP without xsuaa or xssec
Last released April 2022 at 0.0.2, and no repository is declared on the package.
Identity Authentication and Identity Provisioning as one tenant
OAuth2 token validation from XSUAA and SAP Cloud Identity Services
Former XSUAA JWT validation for CAP Java, removed in CAP Java 3.0
OAuth server issuing JWTs and holding scopes for BTP apps
Authorization from DCL policies for Node.js apps on SAP Cloud Identity
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
Utility bundle for CAP handlers: builder, roles, validation, queries
It is a bundle rather than a plugin with one job, and a single release from March 2026 — depending on it for the query helpers brings the auth and validation layers too.
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.
Maven bill of materials pinning CAP Java module versions
OAuth server issuing JWTs and holding scopes for BTP apps
Change history for annotated CAP entities
CDS plugin for OData change tracking in CAP applications
Change log of annotated entity fields for CAP Java
CAP integration with SAP Data Privacy Integration
CAP Node.js runtime
CAP Node.js runtime
Utility bundle for CAP handlers: builder, roles, validation, queries
It is a bundle rather than a plugin with one job, and a single release from March 2026 — depending on it for the query helpers brings the auth and validation layers too.
Custom messages and handler classes for CAP input validation
Zod schemas as CAP validation middleware
Maven bill of materials pinning CAP Java module versions
CAP plugin validating input against @Validator JSON Schema rules
Quiet Release and repository quiet for 30 months.
Functional boundary The annotation sits on a single element, so a rule that spans two fields, or one that needs a lookup, has nowhere in it to go.
Scans uploaded files over REST with ClamAV
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.
API proxies with security and traffic policies and Developer Hub
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.
Vault for an application's passwords, keys and keyrings
Groups npm audit findings by root dependency, with failing thresholds
It audits through npm: a project that resolves its dependencies with another package manager, or has no `package.json`, has nothing for it to run. What it reports is what `npm audit` knows, so a vulnerability outside the npm advisory data is not in its table.
Command line client and development toolkit for CAP
Groups npm audit findings by root dependency, with failing thresholds
It audits through npm: a project that resolves its dependencies with another package manager, or has no `package.json`, has nothing for it to run. What it reports is what `npm audit` knows, so a vulnerability outside the npm advisory data is not in its table.
GitHub Action setting up the Cloud Foundry CLI
Predefined CI/CD pipelines for SAP development projects
Connects a running CAP application to the CAP console
Inspects database entities and contents at CAP service level
Command line client and development toolkit for CAP
Endpoint discovery for CAP services deployed to Cloud Foundry
Static end-to-end tracer of one CAP operation across repositories
Connects a running CAP Java app to CAP console for monitoring
Browser dashboard for a running CAP Java service during development
Attaches a debugger to a CAP app running on Cloud Foundry
Language server for CDS
OData annotation features for the @sap/vscode-cds extension
CDS language support for VS Code and Business Application Studio
Workspace-wide CSN cache for querying CAP entities and columns
Eclipse plugin for the CDS language
Neither the package manifest nor the repository tree declares a licence.
SAP CDS language support for IntelliJ IDEA
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.
Development environment on BTP for UI5, Fiori, mobile and CAP
CDS language support for the Zed editor
Interactive generator for CAP event handler files
Interactive project installer for CAP Node.js
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.
Command line for changing features of an existing Fiori project
Writer of flexible programming model elements into Fiori elements apps
Shared functions and types of the Fiori generators
Writer that adds an OData service to an existing UI5 project
Command line client and development toolkit for CAP
CAP project generator behind SAP Business Application Studio's wizard
CDS project generator, deprecated in favour of @sap/cds-dk
Maven plugin running CDS build steps in a CAP Java project
Maven archetype generating a new CAP Java project
Joule's generative AI inside SAP Build Code
Development environment on BTP for UI5, Fiori, mobile and CAP
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
Browser dashboard for a running CAP Java service during development
Maven plugin running CDS build steps in a CAP Java project
Dev-time wrapper for the SAP Application Router
Serves a Vite app through cds watch and imports .cds files
Command line client and development toolkit for CAP
AWK script sketching an ER diagram from .cds files
No published releases; repository quiet for 26 months.
Command line client and development toolkit for CAP
Maven bill of materials pinning CAP Java module versions
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
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
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
Maven bill of materials pinning CAP Java module versions
Static check that each exported TypeScript function has a test
It reads TypeScript exports only; a project written in plain JavaScript has no exported functions for it to extract. A call to the function name in a test file counts as tested, and a call through property access such as `.foo(` does not.
Terminal UI running Bruno collections against a CAP service
Decorator-driven handler registration for CAP in TypeScript
Typed BaseRepository over CAP entities
Convention-based handler layer for CAP with draft lifecycle hooks
Typed class-based service layer over CAP ApplicationService
Last released July 2022, and no repository is declared on the package.
One handler file per entity in CAP services
CDS build task compiling TypeScript sources during cds build
Decorator-based routing of CAP service handlers in TypeScript
Release and repository quiet for 46 months.
CLI generating TypeScript interfaces from a CDS model
Generates TypeScript types from a CDS model
Type definitions for the CAP Node.js SDK
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.
Maven plugin running CDS build steps in a CAP Java project
CAP Node.js runtime
Declarative status-transition flows on bound actions in CAP Java
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
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.
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.
UI5 app consuming the cds-bookshop server via ui5-middleware-cap
