onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
CLICLItypeA command you run, rather than a dependency you import.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

@sap/cds-dk

The command line client and development toolkit for CAP projects, with the commands cds build, cds deploy, cds watch and cds add among them.

npm92,467/wk
Docs

Facts

Latestv10.2.0ReleasedLicenceSAP DEVELOPER LICENSE AGREEMENT 3.2 CAP

Where it sits

Lives in
CAP
Provides
GeneratorsCAPGeneratorscapabilityGetting from nothing to a project that runs, and from a project that runs to one that has the piece you just decided you need. Two different moments: the first is a one-time decision about layout, the second recurs for the life of the project.Local developmentCAPLocal developmentcapabilityRunning the whole stack on a laptop against real bindings — the service, the UI and the routing in front of it — without deploying to see a change.DeploymentCAPDeploymentcapabilityGetting an application onto a runtime and keeping it there: build descriptors, deployment topology, service bindings and lifecycle operations. The target runtime determines how the application is packaged and configured.Native SAP HANA artifactsCAPNative SAP HANA artifactscapabilityUsing native SAP HANA database objects alongside an application’s generated data model, including objects and database features the modelling layer cannot express. Choosing a database is [database connectors](capability:database-connectors); changing an existing schema is [schema evolution](capability:schema-evolution).CI/CD pipelinesCAPCI/CD pipelinescapabilityA pipeline that builds, tests and delivers an application each time its source repository changes, with a build log that shows which step failed. [Deployment](capability:deployment) describes getting the build onto its target runtime.Plugin authoringCAPPlugin authoringcapabilityWriting a package that extends a framework or runtime rather than an application that uses it — a reusable extension loaded by its host, and the question you arrive at once solving a problem twice makes you want to solve it once for everyone.DebuggingCAPDebuggingcapabilitySeeing what running code did between an input arriving and a result coming out: which code ran, what the values were at each point, and why a value ended up as it did.Model visualisationCAPModel visualisationcapabilityTurning a data or code model into a readable picture of its entities, classes, fields and relationships, so a reader can understand the shape of a domain without opening every source file.Service integrationCAPService integrationcapabilityUsing a service that runs somewhere else as if it were one of your own: its API imported into the model, a proxy that turns a local query into the remote protocol, and a mock that stands in for it on a laptop. Distinct from [destinations](capability:destinations), which is how the address and the credentials are found, and from [replication](capability:replication), which is holding the data locally.
Flavors
Node.jsfrom its runtime

Before choosing this

Conditions

LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2from DeploymentA productive CAP customer application is deployed using materials covered by this agreement.
  • § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
  • § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.

The CAP-specific agreement makes the deployment platform part of the permitted productive-use condition, so deployment choices need the applicable agreement checked rather than treated as purely technical.

SAP Developer License Agreement 3.2 CAP →
LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2from Plugin authoringA plugin is developed or distributed for use with SAP CAP materials covered by the agreement.
  • § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
  • § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.

The agreement expressly includes plug-ins among the SAP materials and section 2 addresses making APIs and tools available to third parties. A plugin's own open-source licence does not erase those separate use terms.

SAP Developer License Agreement 3.2 CAP →

What it declares

Every artifact

Type
CLI
Origin
By SAP
Runtime
Node.js

As a CLI

Distributed through
does not say

For local development

Supports
Binds cloud servicesCredentials on disk
Part of the local stack it starts
CAP serviceApp Router
property statedstated nonot said

Tasks this contributes to4Beta

Local development4
Open a CAP application through its router locallyA developer opens the application on a laptop at the address the App Router serves, logs in through the real authentication flow, and reaches the CAP service and the UI modules behind it the way a deployed request would.Node.jsShown workingthe documented two-process setup
What it does

cds add approuter puts the router in the project, and cds bind --exec -- npm start starts it on port 5000 with the credentials of the bound XSUAA instance, with the service running beside it under the hybrid profile.

Conditions

an XSUAA or SAP Identity service instance exists in the cloud and is bound with cds bind, since the credentials the router starts with come from that binding; the CAP application runs beside the router with the hybrid profile

Remaining work

Create the service instance and the service key in the cloud, bind them, and keep two processes running. The router itself needs no restart on a file change, since it serves static files or delegates to the backend service.

All options on the Local development page →
Pick up a CDS model change without restarting by handA developer edits a CDS file or a handler and the running service answers the next request against the changed model, without stopping and starting it.Node.js, JavaCoversthe watch loop (Node.js)
What it does

cds watch watches for changed files and restarts the Node.js server, so the next request is served against the saved model.

Remaining work

Nothing beyond running it. The restart follows any changed file the project holds, seed data included, which is the loop working as documented rather than a setting.

All options on the Local development page →
Run a CAP service against a cloud service instanceA service running on a laptop reads and writes through a service instance that exists in the cloud — a database, a destination, an authentication service — instead of through the local substitute, with nothing deployed.Node.js, JavaShown workingthe binding and the profile
What it does

cds bind records where the credentials can be obtained rather than the credentials themselves, and reaches a managed, a user-provided or a shared Cloud Foundry instance as well as a Kubernetes service binding or a plain secret. The run then starts under that profile: cds watch --profile hybrid on Node.js, and cds bind --exec mvn spring-boot:run for a CAP Java application.

Conditions

the developer is logged in to the target Cloud Foundry space or Kubernetes cluster, which is where cds bind resolves the instance from; the same profile name is used to create the binding and to run, since bindings are assigned to the hybrid profile by default

Remaining work

Create the instance and its service key in the cloud and keep the profile name consistent. The binding is resolved when the process starts, so a service only reachable through a tunnel still needs the tunnel.

All options on the Local development page →
Start a CAP service with nothing boundA CAP project whose model imports a remote service and whose endpoints are authenticated starts, serves and answers requests on a laptop with no service instance bound, no database provisioned and no upstream system reachable.Node.js, JavaCoversthe command that starts it
What it does

cds watch starts the server and the artifacts the in-memory SQLite database needs are created as it runs, with no build step in a Node.js project; cds mock runs the imported service in a separate process where one process is too far from the target setup.

Remaining work

Nothing beyond running it. The database is reset on each application start, so seed data is the only data a fresh run has.

All options on the Local development page →

Connections21

Download
@sap/cds-dk connections@sap/cds-dkPROVIDES→ provides9provides stated cds add github-actions writes the workflows that test a push, deploy the main branch to staging on Cloud Foundry or Kyma from repository or organisation variables, and deploy to production when a release is published. Deploy using CI/CD Pipelines — capire: https://cap.cloud.sap/docs/guides/deploy/cicd Deploy using CI/CD Pipelines — capire: https://cap.cloud.sap/docs/guides/deploy/cicd Deploy using CI/CD Pipelines — capire: https://cap.cloud.sap/docs/guides/deploy/cicdCI/CD pipelinesprovides stated cds debug starts a local application in debug mode or puts an already running application on SAP BTP Cloud Foundry into it. CDS Command Line Interface — capire: https://cap.cloud.sap/docs/tools/cds-cli#debugging-with-cds-debugDebuggingprovides stated Compiles the project into the deployment layout with cds build — HDI artifacts, the Node.js or Java module, the MTX sidecar — as the step before any platform deploy. Customizing cds build — capire: https://cap.cloud.sap/docs/guides/deploy/buildDeploymentprovides stated Creates the project with cds init and expands it one facet at a time with cds add — a database, messaging, authentication, a deployment descriptor. CDS Command Line Interface — capire: https://cap.cloud.sap/docs/tools/cds-cliGeneratorsprovides stated Runs the service with cds watch, restarting on changed files, and binds a local run to real service instances through the hybrid profile: cds bind keeps only where the credentials can be obtained on the machine, and cds bind --exec starts a Java application, or the App Router from the project's own folder, with the same bindings. cds CLI — cds watch: https://cap.cloud.sap/docs/tools/cds-cli#cds-watch Inner-Loop Development — capire: https://cap.cloud.sap/docs/guides/integration/inner-loops Hybrid Testing — cds bind: https://cap.cloud.sap/docs/tools/cds-bind Authentication (Node.js) — capire, running the App Router: https://cap.cloud.sap/docs/node.js/authenticationLocal developmentprovides stated cds compile --to mermaid emits a Mermaid class diagram from a model, since @sap/cds-dk 8.0.0. cds CLI — cds compile --to mermaid: https://cap.cloud.sap/docs/tools/cds-cli#mermaidModel visualisationprovides stated cds build copies the native design-time files under db/src, an .hdbtable, .hdbsynonym or .hdbindex, untouched into gen/db/src beside the generated HDI artifacts, so they deploy in the same container. Using Native HANA Artifacts — capire: https://cap.cloud.sap/docs/guides/databases/hana-native Using SAP HANA Cloud for Production — capire: https://cap.cloud.sap/docs/guides/databases/hanaNative SAP HANA artifactsprovides stated Runs the build plugins a package registers with cds.build from its cds-plugin.js as part of cds build, and takes a build task type the plugin contributes to the cds schema. Implement Build Plugins — capire: https://cap.cloud.sap/docs/tools/apis/cds-build Plugins for cds add — capire: https://cap.cloud.sap/docs/tools/apis/cds-add CDS Design Time APIs — capire: https://cap.cloud.sap/docs/tools/apis/Plugin authoringprovides stated cds import converts an OData EDMX, an OpenAPI or an AsyncAPI file to CSN, the model of the remote service a consuming project then connects to; cds.import does the same from JavaScript. CDS Import API — capire: https://cap.cloud.sap/docs/tools/apis/cds-importService integrationUSED BY← needed by5needed by derived the dev kit behind `cds watch` for a local run and `cds build --production` in the MTA build Through: inverted from its requires edge lemaiwo/btp-agent — CLAUDE.md, Key Dependencies: https://raw.githubusercontent.com/lemaiwo/btp-agent/main/CLAUDE.md Agentic AI on BTP: a Single Agent with LangGraph — SAP Community, local development: https://community.sap.com/t5/technology-blog-posts-by-members/agentic-ai-on-btp-a-single-agent-with-langgraph/ba-p/14388025btp-agentneeded by derived The scaffolding step is the real `cds init` and `cds add` commands, invoked either from a global install or through npx pinned to the version the project declares. Through: inverted from its requires edge cap-mtx-scaffold — README, Quickstart requirements: https://github.com/fermeregali/cap-mtx-scaffoldcap-mtx-scaffoldneeded by derived the CDS command line the application is started with, globally installed or run through npx Through: inverted from its requires edge SAP-samples/cloud-integration-pipeline-datastore-extension-ui — README, Quick Start (local): https://github.com/SAP-samples/cloud-integration-pipeline-datastore-extension-uicloud-integration-pipeline-datastore-extension-uineeded by derived Compiling the CDS model to CSN needs a Node.js runtime with the [@sap/cds-dk](artifact:sap-cds-dk) development kit, which the plugin installs and runs itself unless a global installation is used. Through: inverted from its requires edge Building Applications: https://cap.cloud.sap/docs/java/developing-applications/buildingcom.sap.cds:cds-maven-pluginneeded by derived `cds watch`, the command the README gives for running the project. Through: inverted from its requires edge ui5-cap-serverside-rendering-demo — README, Next Steps: https://github.com/lemaiwo/ui5-cap-serverside-rendering-demo ui5-cap-serverside-rendering-demo — package.json, devDependencies: https://raw.githubusercontent.com/lemaiwo/ui5-cap-serverside-rendering-demo/main/package.jsonui5-cap-serverside-rendering-demo← optionally used by3optionally used by derived If: the project provides no local CDS Supplies the @sap/cds runtime version the model is compiled with when the project itself provides none. Through: inverted from its requires edge cap-js/mcp-server — CHANGELOG, 0.0.7: https://raw.githubusercontent.com/cap-js/mcp-server/main/CHANGELOG.md@cap-js/mcp-serverifoptionally used by derived If: CAP development Needed for CAP development work, per the README's own requirements list. Through: inverted from its requires edge sap-power README: https://github.com/mfigueir/sap-powerSAP Power for Kiroifoptionally used by derived If: the CAP framework option is used compiling the CDS service before the MTA build for [CAP](artifact:sap-cds-dk) agents Through: inverted from its requires edge joule-a2a-agent-toolkit: skills/joule-a2a-agent/references/cf-deployment-cap-typescript.md: https://raw.githubusercontent.com/SAP-samples/joule-a2a-agent-toolkit/main/skills/joule-a2a-agent/references/cf-deployment-cap-typescript.mdSAP-samples/joule-a2a-agent-toolkitif← used by4used by derived Through: inverted from its requires edge@khalidmh/capxused by derived when using the cap-development skill after jl init, to build and run CAP [Node.js](external:nodejs) applications Through: inverted from its requires edge @sap/joule-studio-cli — skill prerequisites: https://www.npmjs.com/package/@sap/joule-studio-cli@sap/joule-studio-cliused by derived the cap-development skill the backend hands the coding agent, which builds and runs CAP Node.js applications Through: inverted from its requires edge @sap/joule-work-dev-cli-early-adopters — npm, README: https://www.npmjs.com/package/@sap/joule-work-dev-cli-early-adopters@sap/joule-work-dev-cli-early-adoptersused by derived creating the target CAP project and building it, which the steps do with `cds init`, `cds add hana` and `cds build --production`. Through: inverted from its requires edge SAP-samples/xsa-cap-migration — README, Requirements: https://github.com/SAP-samples/xsa-cap-migrationxsa-cap-migration

Install

npm add @sap/cds-dk

Derived from the package name. No recipe recorded; the README has the configuration.

Learn more2

Readings
  1. CAP in the age of AI #7 - vector embeddings wrap-upDJ Adams, Johannes Vogt, YouTube — SAP Developers playlists
  2. Building an SAP BTP Agent Architecture from Scratch: Python + CAP + HANAneilaspin, SAP Community

README

quoted from @sap/cds-dk@10.1.0, read
@sap/cds-dk@10.1.0/readme.mdOn npm

@sap/cds-dk

The command line client and development toolkit for the SAP Cloud Application Programming Model (CAP).

See the documentation for more details.

excerpt, SAP DEVELOPER LICENSE AGREEMENT 3.2 CAP, read licencethe rest, on npm

History

Latest

v10.2.0

Features 10, Fixes 19

  1. v10.1.2

    Fixes 7

  2. v10.1.1

    Features 1, Fixes 3

  3. v10.1.0

    Features 10, Changed 5, Fixes 29

  4. v10.0.9

    Fixes 1

  5. v10.0.8

    Changed 1

  6. v10.0.7

    Changed 1, Fixes 4

  7. v10.0.6

    Features 1, Changed 3, Fixes 16

  8. v10.0.5

    Fixes 18

  9. v10.0.4

    Fixes 1

  10. v10.0.3

    Fixes 3

  11. v10.0.2

    Fixes 3

  12. v10.0.1

    Features 4, Changed 9, Fixes 12

  13. v10.0.0

    Removed 4, Features 5, Changed 4, Fixes 7

  14. v9.9.5

    Changed 1

  15. v9.9.4

    Changed 2

  16. v9.9.3

    Fixes 2

  17. v9.9.2

    Fixes 2

  18. v9.9.1

    Changed 1, Fixes 5

  19. v9.9.0

    Features 3, Changed 3, Fixes 5

  20. v9.8.3

    Fixes 2

  21. v9.8.2

    Features 1, Fixes 3

  22. v9.8.1

    Fixes 2

  23. v9.8.0

    Features 6, Changed 5, Fixes 6

  24. v9.7.2

    Fixes 5

  25. v9.7.1

    Fixes 5

  26. v9.7.0

    Features 6, Changed 8, Fixes 9

  27. v9.6.1

    Changed 1, Fixes 5

  28. v9.6.0

    Features 1, Changed 4, Fixes 10

  29. v9.5.0

    Features 1, Changed 18, Fixes 6

  30. v9.4.3

    Features, Changed 6, Fixes 6

  31. v9.4.2

    Changed 4, Fixes 7

  32. v9.4.1

    Features 2, Fixes 2

  33. v9.4.0

    Features 4, Changed 8, Fixes 5

  34. v9.3.2

    Fixes 2

  35. v9.3.1

    Fixes 11

  36. v9.3.0

    Features 5, Changed 2, Fixes 2

  37. v9.2.1

    Changed 4, Fixes 5

  38. v9.2.0

    Features 5, Changed 10, Fixes 3

  39. v9.1.3

    Fixes 1

  40. v9.1.2

    Fixes 2

  41. v9.1.1

    Features 1, Changed 1, Fixes 2

  42. v9.1.0

    Features 2, Changed 3, Fixes 9

  43. v9.0.6

    Changed 2

  44. v9.0.5

    Changed 1, Fixes 3

  45. v9.0.4

    Changed 1, Fixes 3

  46. v9.0.3

    Changed 7, Fixes 2

  47. v9.0.2

    Fixes 3

  48. v9.0.1

    Removed 4, Features 2, Changed 21, Fixes 10

  49. v8.9.14

    Fixes 1

  50. v8.9.13

    Fixes 1

  51. v8.9.12

    Fixes 3

  52. v8.9.11

    Fixes 1

  53. v8.9.10

    Fixes 1

  54. v8.9.9

    Fixes 1

  55. v8.9.8

    Fixes 1

  56. v8.9.7

    Fixes 1

  57. v8.9.6

    Fixes 1

  58. v8.9.5

    Fixes 3

  59. v8.9.4

    Changed 1

  60. v8.9.3

    Changed 1, Fixes 2

  61. v8.9.2

    Changed 2, Fixes 2

  62. v8.9.1

    Fixes 4

  63. v8.9.0

    Removed 1, Features 4, Changed 2, Fixes 2

  64. v8.8.2

    Fixes 1

  65. v8.8.1

    Fixes 4

  66. v8.8.0

    Features 4, Changed 4, Fixes 7

  67. v8.7.3

    Fixes 5

  68. v8.7.2

    Fixes 9

  69. v8.7.1

    Fixes 6

  70. v8.7.0

    Features 5, Changed 4, Fixes 5

  71. v8.6.1

    Fixes 1

  72. v8.6.0

    Features 8, Changed 1, Fixes 5

  73. v8.5.1

    Fixes 1

  74. v8.5.0

    Features 7, Changed 4, Fixes 6

  75. v8.4.2

    Changed 1, Fixes 7

  76. v8.4.1

    Features 2, Fixes 6

  77. v8.4.0

    Features 5, Changed 3, Fixes 8

  78. v8.3.0

    Features 8, Changed 2, Fixes 2

  79. v8.2.3

    Fixes 5

  80. v8.2.2

    Fixes 5

  81. v8.2.1

    Fixes 2

  82. v8.2.0

    Removed 1, Features 13, Changed 3, Fixes 6

  83. v8.1.2

    Fixes 3

  84. v8.1.1

    Features 2, Changed 1, Fixes 9

  85. v8.1.0

    Features 2, Changed 1, Fixes 13

  86. v8.0.3

    Fixes 11

  87. v8.0.2

    Features 1, Changed 5

  88. v8.0.1

    Features 7, Changed 8, Fixes 5

  89. v8.0.0

    Removed 1, Features 15, Changed 36, Fixes 8

On unpkg
92,691downloads per week, npm
Weekly downloads for @sap/cds-dk26 complete calendar weeks from 2026-04-20 to 2026-10-18; the latest total is 92691.20 Apr – 26 Apr: 176,37327 Apr – 3 May: 158,4304 May – 10 May: 174,96611 May – 17 May: 183,50118 May – 24 May: 185,28225 May – 31 May: 171,5341 Jun – 7 Jun: 142,7888 Jun – 14 Jun: 187,47815 Jun – 21 Jun: 187,84822 Jun – 28 Jun: 180,85729 Jun – 5 Jul: 186,9206 Jul – 12 Jul: 197,87713 Jul – 19 Jul: 205,77220 Jul – 26 Jul: 201,38627 Jul – 2 Aug: 202,2183 Aug – 9 Aug: 198,97010 Aug – 16 Aug: 162,57617 Aug – 23 Aug: 186,72824 Aug – 30 Aug: 182,25631 Aug – 6 Sept: 138,1457 Sept – 13 Sept: 120,22114 Sept – 20 Sept: 140,93721 Sept – 27 Sept: 177,72628 Sept – 4 Oct: 185,3215 Oct – 11 Oct: 173,51712 Oct – 18 Oct: 92,691

Others providing40

Generators
  1. SAP Build CodeDevelopment environment on BTP for UI5, Fiori, mobile and CAP
  2. @cap-handler/generatorInteractive generator for CAP event handler files
  3. com.sap.cds:cds-maven-pluginMaven plugin running CDS build steps in a CAP Java project
  4. com.sap.cds:cds-services-archetypeMaven archetype generating a new CAP Java project
  5. @khalidmh/capxInteractive project installer for CAP Node.js
  6. Joule in SAP Build CodeJoule's generative AI inside SAP Build Code
  7. @sap/generator-cap-projectCAP project generator behind SAP Business Application Studio's wizard
  8. @sap/generator-cdsCDS project generator, deprecated in favour of @sap/cds-dk
  9. @sap-ux/cap-config-writerWriter module for changing a CAP project's configuration from code
  10. @sap-ux/createCommand line for changing features of an existing Fiori project
  11. @sap-ux/fe-fpm-writerWriter of flexible programming model elements into Fiori elements apps
  12. @sap-ux/fiori-generator-sharedShared functions and types of the Fiori generators
  13. @sap-ux/odata-service-writerWriter that adds an OData service to an existing UI5 project
Local development
  1. vite-plugin-cdsServes a Vite app through cds watch and imports .cds files
  2. com.sap.cds:cds-feature-dev-dashboardBrowser dashboard for a running CAP Java service during development
  3. com.sap.cds:cds-maven-pluginMaven plugin running CDS build steps in a CAP Java project
  4. @cap-js-community/commonSix CAP features in one package, from replication cache to rate limits
  5. @neoimpulse/cap-js-bootstrapCLI starting several CAP services and an AppRouter locally together
  6. @sang2x/captoolsCLI of CAP development tools for Cloud Foundry workflows
  7. @sap/ams-devCompiler from AMS DCL policies to DCN for local runs and tests
  8. @sap/cdsCAP Node.js runtime
  9. dev-approuterDev-time wrapper for the SAP Application Router
Deployment
  1. @cap-js/cap-operator-pluginGenerates Helm charts for the CAP Operator on Kubernetes
  2. @rizing/cds-customer-stepbystep-toolTool completing a CAP project's deployment configuration
Native SAP HANA artifacts
  1. cds-federation-synonymsCAP-to-CAP data federation over SAP HANA synonyms
  2. @sap/cdsCAP Node.js runtime
  3. @sap/hdi-deployNode.js deployer for SAP HANA Deployment Infrastructure containers
  4. SAP-samples/hana-developer-cli-tool-exampleDeveloper-centric command line for SAP HANA
CI/CD pipelines
  1. SAP Continuous Integration and DeliveryPredefined CI/CD pipelines for SAP development projects
  2. cf-setupGitHub Action setting up the Cloud Foundry CLI
  3. audit-summaryGroups npm audit findings by root dependency, with failing thresholds
Plugin authoring
  1. com.sap.cds:cds-services-bomMaven bill of materials pinning CAP Java module versions
Debugging
  1. com.sap.cds:cds-feature-consoleConnects a running CAP Java app to CAP console for monitoring
  2. com.sap.cds:cds-feature-dev-dashboardBrowser dashboard for a running CAP Java service during development
  3. @cap-js/consoleConnects a running CAP application to the CAP console
  4. @cap-js/data-inspectorInspects database entities and contents at CAP service level
  5. sap-cap-debuggerAttaches a debugger to a CAP app running on Cloud Foundry
  6. @saptools/cf-request-runnerEndpoint discovery for CAP services deployed to Cloud Foundry
  7. @saptools/service-flowStatic end-to-end tracer of one CAP operation across repositories
Model visualisation
  1. sap-cds-erdAWK script sketching an ER diagram from .cds files
Service integration
  1. com.sap.cds:cds-feature-remote-odataRemote Services for consuming OData V2 and V4 APIs in CAP Java
  2. capire/s4Prebuilt SAP S/4HANA integration package for CAP projects
  3. cds-data-federationData federation for CAP via delegation, caching and replication
  4. @sap/cdsCAP Node.js runtime

Details

Sources4
npm registrydiscovered herechecked
GitHub APIdiscovered here, cap-jschecked
npm registry, @sap/cds-dkversion, releases, installschecked
readme.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
latestv10.2.0
first release
releases and cadence225, ~3d median
discovered vianpm registry, GitHub API · cap-js
first seen in the atlas
ecosystem and domaincap, developer-experience
History in the atlas2
  1. The same, plus what cds bind keeps on the machine and the exec form that starts a Java application or the App Router, with the three comparison values this capability now declares.
  2. First seen.
For your agent
Ref
artifact:sap-cds-dk
JSON
/artifacts/sap-cds-dk.json
MCP
Connecting an agent