Everything in CAP / Java
Type: 4
Domain
Origin
Signals
Java: Answers in Java
More
Group by: Capability
Where it runs
Distributed through
Maven bill of materials pinning CAP Java module versions
Generates Open Resource Discovery documents from a CAP Java model
OData V2 protocol adapter built into the CAP Java runtime
OData V4 protocol adapter for CAP Java Application Services
Maven bill of materials pinning CAP Java module versions
API proxies with security and traffic policies and Developer Hub
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.
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 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.
APIs and a UI5 component for document management in apps
Managed Redis from the hyperscaler via a BTP service binding
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions
SAP's Node.js driver for SAP HANA
SAP HANA Cloud datasource for CAP Java applications
JDBC runtime for H2 and SQLite in CAP Java
PostgreSQL datasource for CAP Java applications
Maven bill of materials pinning CAP Java module versions
Managed PostgreSQL from the hyperscaler via a BTP service binding
Managed SAP HANA database service on BTP
Provisioned per plan and per component, so capacity and cost are decisions taken before any model exists. And it is the database, not a warehouse — modelling, loading and cataloguing are the products above it, and reaching it directly bypasses every semantic they add.
Developer-centric command line for SAP HANA
Fork of cds-dbm with deploy, load, diff and drop tasks
Release and repository quiet for 39 months.
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions
Managed queues and topics over AMQP, MQTT and REST
Remote Services for consuming OData V2 and V4 APIs in CAP Java
SAP Cloud SDK integration for remote REST services in CAP Java
Named, credentialed addresses of other systems resolved at runtime
CAP Java plugin for SAP Integration Suite, advanced event mesh
Connects CAP Java messaging to SAP Event Mesh
Connects CAP Java messaging to SAP Cloud Application Event Hub
Connects CAP Java messaging to Apache Kafka
Beta connector from CAP Java messaging to Redis Pub/Sub
Maven bill of materials pinning CAP Java module versions
Managed queues and topics over AMQP, MQTT and REST
Event streaming and management platform in Integration Suite
Business notifications from CAP Java via SAP Alert Notification
Proxy from cloud apps to on-premise systems via Cloud Connector
Maven bill of materials pinning CAP Java module versions
Remote Services for consuming OData V2 and V4 APIs in CAP Java
Developer-centric command line for SAP HANA
Agent skills for CAP development, each a SKILL.md with references
SAP's capire/skills packaged for the pi coding agent
If your tool reads the open skill standard directly, install [capire/skills](artifact:capire-skills) and skip the wrapper.
CAP review skill for coding agents with gates and prohibitions
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary There is no licence, so there is no grant to use or redistribute it. Everything else is secondary to that. Note too that its 'verified' claim means the skill text was checked against itself by an evaluation suite — not that the advice was run against a CAP version.
Agent skills for CAP development, each a SKILL.md with references
SAP skills for the Kiro IDE
Host-specific: outside Kiro the automatic context activation is the part that does not come with it, and what remains is prose you would have to wire in yourself. Breadth over depth by design — thirty-five skills across six product areas is an orientation layer, not a substitute for the focused sets in each.
Agent skill for SAP Customer Experience APIs, CDS and errors
Forty SAP development plugins for coding agents
GPL-3.0, which is a licence to read before vendoring any of it into something you ship. Forty plugins is also a lot of always-available surface — the ledger is there because breadth and verification pull in opposite directions, and it does not resolve that so much as report it.
CLI for Joule digital assistants and Joule Studio solutions
Pro-code CLI for building and deploying Joule Studio solutions
A2A adapter turning a CAP Java service into an LLM-backed agent
Low-code SAP Build capability for custom Joule skills and agents
SAP's AI engagement layer across SAP applications
AI runtime on BTP with the Generative AI Hub
AI runtime on BTP with the Generative AI Hub
Extracts header fields and line items from business documents
Bridge from CAP Java to SAP AI Core, with Fiori field recommendations
AI runtime on BTP with the Generative AI Hub
AI runtime on BTP with the Generative AI Hub
AI runtime on BTP with the Generative AI Hub
Managed SAP HANA database service on BTP
Provisioned per plan and per component, so capacity and cost are decisions taken before any model exists. And it is the database, not a warehouse — modelling, loading and cataloguing are the products above it, and reaching it directly bypasses every semantic they add.
API proxies with security and traffic policies and Developer Hub
Skill assessing API usage against the SAP API Policy
It says so itself, in bold, and the atlas repeats it: not legal advice and not a compliance decision. Only SAP, your contract, or SAP support can answer bindingly, and the skill routes legal, commercial and roadmap questions there rather than guessing at them. Treat the output as evidence gathered, not as a verdict.
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
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
Maven bill of materials pinning CAP Java module versions
OAuth server issuing JWTs and holding scopes for BTP apps
Change log of annotated entity fields for CAP Java
Maven bill of materials pinning CAP Java module versions
Scans uploaded files over REST with ClamAV
API proxies with security and traffic policies and Developer Hub
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.
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.
Reads bound service credentials on SAP BTP, Cloud Foundry for CAP Java
Reads SAP BTP Operator service bindings on Kyma for CAP Java
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions
Boolean and string flags read by applications at runtime
Calls an application endpoint on a schedule and logs each run
Maven bill of materials pinning CAP Java module versions
Collects Cloud Foundry or Kyma logs into a searchable Kibana
Multitenancy for CAP Java: tenant lifecycle and per-tenant containers
Maven bill of materials pinning CAP Java module versions
Registers a multitenant application for subaccount subscriptions
Maven bill of materials pinning CAP Java module versions
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.
Predefined CI/CD pipelines for SAP development projects
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
Attaches a debugger to a CAP app running on Cloud Foundry
Workspace-wide CSN cache for querying CAP entities and columns
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
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
Writer that adds an OData service to an existing UI5 project
Development environment on BTP for UI5, Fiori, mobile and CAP
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.
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.
AWK script sketching an ER diagram from .cds files
No published releases; repository quiet for 26 months.
Maven bill of materials pinning CAP Java module versions
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
Managed hosting and routing for built frontends
SAP's own guidance is narrower than the service's reach: it names standalone, single-tenant applications that do not connect to other applications as the fit, and says to stay on [the HTML5 Application Repository](artifact:btp-html5-application-repository) and the application router where those meet your needs better. Four hard limits decide it before taste does — 300 requests per second per subaccount, ten retained versions per application, 100 MB per application and 400 MB for the deployment archive.
Stores UI5 and HTML5 apps and serves them through the approuter
Maven bill of materials pinning CAP Java module versions
OASIS and SAP OData vocabularies with a VocabularyService
Maven bill of materials pinning CAP Java module versions
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.
Reader and writer for i18n bundles of UI5 or CAP projects
Maven bill of materials pinning CAP Java module versions
Declarative status-transition flows on bound actions in CAP Java
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.
Binding onto hyperscaler object storage, chosen by plan
Cloud Foundry runtime of SAP BTP for polyglot applications
One inbox for tasks across SAP applications and BTP workflows