Everything in CAP / Java
Type
Domain
Origin
Signals
Java: Answers in Java
More: 2
Group by: Capability
Maven bill of materials pinning CAP Java module versions
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
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.
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions
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
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
Remote Services for consuming OData V2 and V4 APIs in CAP Java
SAP Cloud SDK integration for remote REST services in CAP Java
Connects CAP Java messaging to SAP Event Mesh
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
Maven bill of materials pinning CAP Java module versions
Remote Services for consuming OData V2 and V4 APIs in CAP Java
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.
A2A adapter turning a CAP Java service into an LLM-backed agent
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 handler for SAP Audit Log service API version 2
Maven bill of materials pinning CAP Java module versions
OAuth2 token validation from XSUAA and SAP Cloud Identity Services
Maven bill of materials pinning CAP Java module versions
Change log of annotated entity fields for CAP Java
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.
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
Maven bill of materials pinning CAP Java module versions
Multitenancy for CAP Java: tenant lifecycle and per-tenant containers
Maven bill of materials pinning CAP Java module versions
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.
Endpoint discovery for CAP services deployed to Cloud Foundry
Static end-to-end tracer of one CAP operation across repositories
Browser dashboard for a running CAP Java service during development
Attaches a debugger to a CAP app running on Cloud Foundry
Workspace-wide CSN cache for querying CAP entities and columns
Interactive generator for CAP event handler files
Interactive project installer for CAP Node.js
Maven plugin running CDS build steps in a CAP Java project
Maven archetype generating a new CAP Java project
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.
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.
Browser dashboard for a running CAP Java service during development
Maven plugin running CDS build steps in a CAP Java project
Maven bill of materials pinning CAP Java module versions
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
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
Maven plugin running CDS build steps in a CAP Java project
Maven bill of materials pinning CAP Java module versions
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.
Maven bill of materials pinning CAP Java module versions
Declarative status-transition flows on bound actions in CAP Java
Versioned specification of the abap2UI5 roundtrip protocol
Neither suite has been run against an ABAP system: the reference backends are the framework transpiled to Node and cap2UI5 on CAP, so what a check does on a real system is open. The portable profile is a subset of 61 controls, filled from a census of 247 core apps of which 64.8 % run unchanged, so an app outside it renders placeholders in the terminal and Adaptive Cards renderers.