Everything in CAP
Type: 2
Domain
Origin
Signals
More
Group by: Kind
Where it runs
Distributed through
Compares a CAP project's CSV data with its database rows
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.
Live-updatable feature toggles for CAP, backed by Redis
CLI for operating tenants of multitenant CAP applications
SDK for SAP Advanced Financial Closing scheduling providers on CDS
Monorepo of CAP's SQL database services
Test support for CAP Node.js: server start, HTTP client, assertions
Type definitions for the CAP Node.js SDK
Base service shared by CAP's SQLite, PostgreSQL and HANA services
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.
CLI for DROP and RENAME schema changes beside @cap-js/postgres
Decorator-driven handler registration for CAP in TypeScript
Typed BaseRepository over CAP entities
Vercel AI SDK provider for SAP AI Core
LangChain vector store on SAP AI Core Document Grounding
LangChain vector store with CDS entities for embeddings
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.
CLI starting several CAP services and an AppRouter locally together
Fork of cds-dbm with deploy, load, diff and drop tasks
Release and repository quiet for 39 months.
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.
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
Destination lookup and connectivity proxy for the Cloud SDK
HTTP client carrying a destination's credentials
Shared machinery under the Cloud SDK's OData and OpenAPI clients
Generated OpenAPI clients for the Cloud SDK
Timeouts, retries and circuit breaking around remote calls
General utilities shared across the Cloud SDK packages
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
Command line for changing features of an existing Fiori project
Writer of flexible programming model elements into Fiori elements apps
Fiori Elements mock server plugin taking a CDS file as metadata
Programmatic API for reading and writing project annotations
Fiori documentation indexed as embeddings
Shared functions and types of the Fiori generators
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
Library for sending usage telemetry data
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
Multitenancy, tenant provisioning and extensibility for CAP
Calls to ABAP function modules over RFC from a CAP service
SAP's Node.js driver for SAP HANA
Node.js deployer for SAP HANA Deployment Infrastructure containers
CLI for Joule digital assistants and Joule Studio solutions
Pro-code CLI for building and deploying Joule Studio solutions
Wrapper around the CDS compiler for annotation handling
Token validation and security context for XSUAA and IAS
Node module for CAP calling external APIs through a destination
Quiet Release and repository quiet for 57 months.
Functional boundary The package declares `@sap/cds` ^4.5.2 among its dependencies and pins `@sap-cloud-sdk/core` at 1.37.1, so a project on CAP 5 or later is outside the range it states.
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
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.
Bridge from CAP Java to SAP AI Core, with Fiori field recommendations
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.
Prebuilt SAP S/4HANA integration package for CAP projects
Toolkit turning a CAP service into tools for agent frameworks
Typed class-based service layer over CAP ApplicationService
Last released July 2022, and no repository is declared on the package.
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.
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.
Zod schemas as CAP validation middleware
CLI generating TypeScript interfaces from a CDS model
Destination resolution and axios calls from CAP configuration
Release and repository quiet for 46 months.
A2A adapter turning a CAP Java service into an LLM-backed agent
MCP adapter turning a CAP Java service into an MCP server
SAP prohibits gateway/proxy use for SAP Application APIs; the Atlas separately excludes CAP wrappers around those APIs from its assessed scope. Data changes require application-defined unbound actions, and the adapter supplies no rate limiting, agent-action audit logging, approval workflows or policy enforcement.
OData V2 protocol adapter built into the CAP Java runtime
OData V4 protocol adapter for CAP Java Application Services
CAP Java plugin for SAP Integration Suite, advanced event mesh
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 sending audit log events to SAP Audit Log service
CAP Java handler for SAP Audit Log service API version 2
Change log of annotated entity fields for CAP Java
Reads bound service credentials on SAP BTP, Cloud Foundry for CAP Java
Connects a running CAP Java app to CAP console for monitoring
Connects CAP Java messaging to SAP Event Mesh
Connects CAP Java messaging to SAP Cloud Application Event Hub
Declarative status-transition flows on bound actions in CAP Java
SAP HANA Cloud datasource for CAP Java applications
OAuth2 token validation from XSUAA and SAP Cloud Identity Services
JDBC runtime for H2 and SQLite in CAP Java
Reads SAP BTP Operator service bindings on Kyma for CAP Java
Connects CAP Java messaging to Apache Kafka
Multitenancy for CAP Java: tenant lifecycle and per-tenant containers
Triggers n8n workflows from CAP Java through the outbox
Business notifications from CAP Java via SAP Alert Notification
Generates Open Resource Discovery documents from a CAP Java model
PostgreSQL datasource for CAP Java applications
Beta connector from CAP Java messaging to Redis Pub/Sub
Remote Services for consuming OData V2 and V4 APIs in CAP Java
Former XSUAA JWT validation for CAP Java, removed in CAP Java 3.0
SAP Cloud SDK integration for remote REST services in CAP Java
Maven bill of materials pinning CAP Java module versions
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.
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.
Shows which feature branches reached which environment branch
A team that does not keep one long-lived branch per environment has no environment branches for it to compare feature branches against. What it reports is the merge state of branches in Git, so it says nothing about whether a merged change has been built or deployed to the environment.
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.
SDK-free TypeScript client for SAP synchronous RFC on Node.js
The maintainer states 0.x is beta with no production SLA, and scopes support deliberately narrowly: direct application-server transport, classic serialization and password authentication on S/4HANA 2023 and NetWeaver 7.50. Anything outside that is untested rather than unsupported.
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.
Developer-centric command line for SAP HANA
Terminal UI running Bruno collections against a CAP service
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.