Everything in the atlas
Type
Domain
Origin
Signals
More: 3
Group by: None
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.
Tool completing a CAP project's deployment configuration
Tied to a specific training repository and last released August 2023. 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.
npx tool adding worked example files to a CAP project
Last released April 2024.
Spreadsheet upload into a CDS entity, parsed on the server
CDS plugin for OData change tracking in CAP applications
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 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
Browser dashboard for a running CAP Java service during development
Connects CAP Java messaging to SAP Event Mesh
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
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
SAP Cloud SDK integration for remote REST services in CAP Java
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
Feature toggle framework for ABAP with a UI5 GUI
Quiet No published releases; repository quiet for 101 months.
Functional boundary Not where a toggle is meant to be switched on in a production system: the maintainer warns that features should never be enabled in a production system.
ABAP Keyword Documentation as Markdown with indexes
The Markdown is a snapshot of whatever help.sap.com served when the pipeline last ran, and the Standard library is scraped from the `latest` index, so which release a page describes follows from the scrape date rather than from anything the corpus states. `package.json` states ISC and the repository carries no LICENSE file, so what the copied SAP documentation may be used for is not stated in it.