CDS pluginCDS plugintypeInstalls into a CAP project and extends the runtime. CAP loads it through cds.requires or the plugin hook.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
cds-mysql
A MySQL and MariaDB database adapter for CAP that connects to a database instance and translates incoming CQL/CQN requests to it; the repository the package declares has been deleted.
MySQL/MariaDB database adapter for CAP. Connects to a database instance and translates incoming CQL/CQN requests to the database.
Retired2026-10the GitHub accountThis account was archived due to Github is not good for open source anymoreSoontao, GitHub profile
Database connectorsCAPDatabase connectorscapabilityConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).
Theo SunTheo SunPersonMaintains this In the atlas: maintains 8, contributes to 3@Soontaomaintainer
Before choosing this
crawled
Conditions
LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2, 3A cds-plugin is used with SAP CAP materials, or an artifact is explicitly identified as a CAP plugin or application.
Derived: the instrument's applicability matches this artifact, checked
§ 1License. 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.
§ 2Intellectual 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.
§ 3Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
Also, from Database connectors§ 1: The connector itself does not decide the licence boundary. Section 1 makes the destination and purpose of extraction relevant, including the scoped exception for interoperability with an SAP product.
PracticalFunctional boundary
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.
What it declares
Every artifact
Type
CDS plugin
Origin
Independently maintained
As a CDS plugin
Distributed through
does not say
declared, How the plugin is installed into a CAP project, as its documentation says.
Connections2
Group by
NodeRelationConditionBasis
Functional2
@cap-js/hana@cap-js/hanacds-pluginSAP HANA database service for CAPsap official, cap
→alternative to
none
authored
alternative to @cap-js/hana
Functional, authored
SAP HANA database service for CAP
Database connectorsDatabase connectorscapabilityConnecting a data model and its queries to a databaseSAP and community, narrow by design
→provides
none
authored
provides Database connectors
Functional, authored
Connecting a data model and its queries to a database
@cap-js/hana@cap-js/hanacds-pluginThe HANA database service — the production default, on the same streamlined architecture as the SQLite and PostgreSQL services.sap official, capSAP HANA database service for CAP
Database connectorsDatabase connectorscapabilityConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to schema evolution.SAP and community, narrow by design
SAP ASE ServiceSAP ASE ServiceserviceSAP ASE database systems and tenant databases on BTP with SAP running the platform operations, used from Java applications on BTP or on premise over SQL, JPA and JDBC.sap official, btpManaged SAP ASE databases on BTP for Java applicationsfrom BTP/BAIP
SAP HANA CloudSAP HANA CloudserviceThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btpManaged SAP HANA database service on BTPfrom BTP/BAIP
SAP HANA Service (SAP Regions) for SAP BTPSAP HANA Service (SAP Regions) for SAP BTPserviceManaged SAP HANA 2.0 database systems in fixed sizes from 64 GB to 1 TB, in SAP's own regions, with tenant databases bound to applications on SAP BTP.sap official, btpManaged SAP HANA 2.0 databases in fixed sizes on SAP BTPfrom BTP/BAIP
PostgreSQL on SAP BTP, hyperscaler optionPostgreSQL on SAP BTP, hyperscaler optionserviceA managed PostgreSQL from the underlying hyperscaler — AWS, Azure, Google Cloud or Alicloud — consumed through a BTP service binding.sap official, btpManaged PostgreSQL from the hyperscaler via a BTP service bindingfrom BTP/BAIP
com.sap.cds:cds-feature-hanacom.sap.cds:cds-feature-hanapackageThe CAP Java feature that wires a Maven application to SAP HANA Cloud, the production default among CAP's supported databases.sap official, capSAP HANA Cloud datasource for CAP Java applicationsfrom CAP
com.sap.cds:cds-feature-jdbccom.sap.cds:cds-feature-jdbcpackageConnects the CAP Java runtime to JDBC databases through the CDS4j JDBC runtime: H2 and SQLite, which capire names for local development and CI tests rather than enterprise use.sap official, capJDBC runtime for H2 and SQLite in CAP Javafrom CAP
com.sap.cds:cds-feature-postgresqlcom.sap.cds:cds-feature-postgresqlpackageThe CAP Java feature that wires a Maven application to PostgreSQL as its datasource beside SAP HANA, with limitations capire lists: schema evolution first, and no multitenancy or extensibility yet.sap official, capPostgreSQL datasource for CAP Java applicationsfrom CAP
com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bompackageThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, capMaven bill of materials pinning CAP Java module versionsfrom CAP
@cap-js/db-service@cap-js/db-servicepackageThe base every CAP database service is built on: the shared query translation and pooling that SQLite, PostgreSQL and HANA specialise rather than reimplement.sap official, capBase service shared by CAP's SQLite, PostgreSQL and HANA servicesfrom CAP
@cap-js/hana@cap-js/hanacds-pluginThe HANA database service — the production default, on the same streamlined architecture as the SQLite and PostgreSQL services.sap official, capSAP HANA database service for CAPfrom CAP
@cap-js/postgres@cap-js/postgrescds-pluginThe PostgreSQL database service — the production option for running CAP off HANA, sharing the base service with the other three.sap official, capPostgreSQL database service for CAPfrom CAP
@cap-js/sqlite@cap-js/sqlitecds-pluginThe SQLite service, in memory during the inner loop — which is why a CAP project runs before anyone has provisioned a database.sap official, capSQLite database service for CAP, in memory during developmentfrom CAP
cap-postgres-btp-connectivitycap-postgres-btp-connectivitycds-pluginConnects a CAP Node.js application to a PostgreSQL database that is not publicly reachable, tunnelling through BTP Connectivity and the Cloud Connector.independent, capTunnels CAP Node.js to a private PostgreSQL via Cloud Connectorfrom CAP
cds-mongodbcds-mongodbcds-pluginMongoDB as a native CAP database service, through Mongoose — CQN reads and writes, managed associations as ObjectId references, $expand resolved by populate, and cds deploy --to mongoose.independent, capMongoDB as a CAP database service through Mongoosefrom CAP
@cds-pgroll/postgres@cds-pgroll/postgrescliThe destructive half of PostgreSQL schema evolution — DROP and RENAME, which CAP's own schema_evolution: alter will not perform — driven from the command line beside @cap-js/postgres.independent, capCLI for DROP and RENAME schema changes beside @cap-js/postgresfrom CAP
hdbhdbpackageSAP's HANA driver for Node.js, written entirely in JavaScript so installing it pulls in no native client, running SQL against SAP HANA and SAP HANA Cloud with streams and prepared statements.sap official, btpPure JavaScript SAP HANA driver for Node.jsfrom BTP/BAIP
@neoimpulse/cap-js-restore-model-defined-types@neoimpulse/cap-js-restore-model-defined-typescds-pluginA CAP plugin that casts values back to the types the CDS model declares after a READ, for the entities you name, where the database driver returned them as strings.independent, capCAP plugin casting read values back to CDS model typesfrom CAP
@quadrio/cds-db2@quadrio/cds-db2cds-pluginA DB2 adapter for CDS, so a CAP model can be deployed to and served from DB2, last released July 2023 and still on npm while the repository it was published from has been deleted.independent, capDB2 adapter for CDSfrom CAP
@sap/cds-hana@sap/cds-hanacds-pluginThe SAP Cloud Application Programming Model's database adapter for SAP HANA, the package a CAP project adds to run its model on a SAP HANA database.sap official, capDatabase adapter for SAP HANA in CAPfrom CAP
@sap/cds@sap/cdspackageThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtimefrom CAP
@sap/hana-client@sap/hana-clientpackageSAP's own Node.js driver for SAP HANA: connect, run SQL and prepared statements, synchronously, through callbacks or as promises, over native client libraries npm installs per platform.sap official, btpSAP's Node.js driver for SAP HANAfrom BTP/BAIP
SAP HANASAP HANAplatformSAP’s relational database platform, which stores application data and executes SQL and SQLScript in the database, available on-premise and as the managed service SAP HANA Cloud.sap official, btpSAP's relational database platform, on-premise and in HANA Cloudfrom BTP/BAIP
SAP-samples/hana-hdbext-promisfied-exampleSAP-samples/hana-hdbext-promisfied-examplepackagePromise-based wrappers around the SAP HANA client libraries for Node.js, Go and Python, replacing nested callbacks with a single async call.sap official, btpPromise-based wrappers around the SAP HANA client librariesfrom BTP/BAIP
cds-pgcds-pgcds-pluginA PostgreSQL adapter for SAP CDS, built by the SAP Mentors community, which gave CAP a Postgres persistence option years before @cap-js/postgres shipped.independent, capPostgreSQL adapter for SAP CDS from the SAP Mentors communityfrom CAP
cap-snowflakecap-snowflakecds-pluginA CAP database adapter for Snowflake with OData V4 support, which the maintainer marks as early development, so its contract is expected to move.independent, capCAP database adapter for Snowflake with OData V4 supportfrom CAP
The maintainer's GitHub profile states that the account was archived (profile changed 2026-10-11); the repositories are gone and the package stays published on npm. His words, quoted and dated, in the field made for a maker's statement about an end; nothing written about the person.
cap-js-cds-dbs is the repository the four SAP database services are published from, not one of them — its README says 'Each of the subfolders is published as individual npm module' — so nothing installs it and nothing is an alternative to it. The edge to @cap-js/hana, a package a project would add instead of this one, stands.
404 from the GitHub API. Found by the first full run of scripts/check-links.mjs — the citation had a checked date and nobody had re-read it.
