Everything in the atlas
Type
Domain
Origin
Signals
More: 4
Group by: Ecosystem
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
CLI converting UI5 i18n properties files to Excel and back
Release and repository quiet for 39 months.
SAP's ABAP tools in VS Code for editing, debugging, ATC and transports
Scripts running the ABAP Developer Edition in Docker
No published releases; repository quiet for 83 months.
ALV table view generated from a DDIC structure
Generic customizing table and reader for ad hoc ABAP parameters
Maps database tables and fields to the CDS views exposing them
Not on the [SAP BTP ABAP environment](artifact:btp-abap-environment) or another cloud ABAP system: the maintainer states the tool is not cloud ready, because the data sources and system tables it reads CDS metadata from are not released for cloud development. It is designed for SAP S/4HANA on-premise or private cloud, and the shipped Fiori application is configured for A4H and developer systems.
Metadata viewer for SAP BW, SAP BPC and SAP BW/4HANA object models
Tool mapping BEx queries to the transport requests carrying them
Release and repository quiet for 50 months.
No published releases; repository quiet for 74 months.
Report searching ABAP source in methods, enhancements, DTPs and more
No published releases; repository quiet for 58 months.
Open SQL editor for ABAP with ALV output
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.
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.
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.