Everything in CAP / Node.js
Type: 3
Domain
Origin
Signals
Node.js: Answers in Node.js
More
Group by: Capability
Distributed through
Runs on
API proxies with security and traffic policies and Developer Hub
APIs and a UI5 component for document management in apps
Managed Redis from the hyperscaler via a BTP service binding
CLI for DROP and RENAME schema changes beside @cap-js/postgres
Managed PostgreSQL from the hyperscaler via a BTP service binding
Managed SAP HANA database service on BTP
Provisioned per plan and per component, so capacity and cost are decisions taken before any model exists. And it is the database, not a warehouse — modelling, loading and cataloguing are the products above it, and reaching it directly bypasses every semantic they add.
Command line client and development toolkit for CAP
Developer-centric command line for SAP HANA
Fork of cds-dbm with deploy, load, diff and drop tasks
Release and repository quiet for 39 months.
Managed queues and topics over AMQP, MQTT and REST
Named, credentialed addresses of other systems resolved at runtime
Managed queues and topics over AMQP, MQTT and REST
Event streaming and management platform in Integration Suite
Proxy from cloud apps to on-premise systems via Cloud Connector
Command line client and development toolkit for CAP
Developer-centric command line for SAP HANA
Local desktop workspace for AI conversations with SAP connectors
CLI for Joule digital assistants and Joule Studio solutions
Pro-code CLI for building and deploying Joule Studio solutions
Low-code SAP Build capability for custom Joule skills and agents
SAP's AI engagement layer across SAP applications
AI runtime on BTP with the Generative AI Hub
AI runtime on BTP with the Generative AI Hub
Extracts header fields and line items from business documents
AI runtime on BTP with the Generative AI Hub
AI runtime on BTP with the Generative AI Hub
AI runtime on BTP with the Generative AI Hub
Managed SAP HANA database service on BTP
Provisioned per plan and per component, so capacity and cost are decisions taken before any model exists. And it is the database, not a warehouse — modelling, loading and cataloguing are the products above it, and reaching it directly bypasses every semantic they add.
API proxies with security and traffic policies and Developer Hub
Ingests and retains compliance audit data from BTP
Identity Authentication and Identity Provisioning as one tenant
OAuth server issuing JWTs and holding scopes for BTP apps
OAuth server issuing JWTs and holding scopes for BTP apps
Scans uploaded files over REST with ClamAV
API proxies with security and traffic policies and Developer Hub
Vault for an application's passwords, keys and keyrings
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.
Command line client and development toolkit for CAP
Boolean and string flags read by applications at runtime
Calls an application endpoint on a schedule and logs each run
Collects Cloud Foundry or Kyma logs into a searchable Kibana
CLI for operating tenants of multitenant CAP applications
Registers a multitenant application for subaccount subscriptions
Command line client and development toolkit for CAP
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.
Predefined CI/CD pipelines for SAP development projects
Command line client and development toolkit for CAP
Endpoint discovery for CAP services deployed to Cloud Foundry
Static end-to-end tracer of one CAP operation across repositories
Attaches a debugger to a CAP app running on Cloud Foundry
Workspace-wide CSN cache for querying CAP entities and columns
Development environment on BTP for UI5, Fiori, mobile and CAP
Command line for changing features of an existing Fiori project
Command line client and development toolkit for CAP
Development environment on BTP for UI5, Fiori, mobile and CAP
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 starting several CAP services and an AppRouter locally together
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.
Command line client and development toolkit for CAP
Command line client and development toolkit for CAP
AWK script sketching an ER diagram from .cds files
No published releases; repository quiet for 26 months.
Command line client and development toolkit for CAP
Compares a CAP project's CSV data with its database rows
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
CLI generating TypeScript interfaces from a CDS model
Managed hosting and routing for built frontends
SAP's own guidance is narrower than the service's reach: it names standalone, single-tenant applications that do not connect to other applications as the fit, and says to stay on [the HTML5 Application Repository](artifact:btp-html5-application-repository) and the application router where those meet your needs better. Four hard limits decide it before taste does — 300 requests per second per subaccount, ten retained versions per application, 100 MB per application and 400 MB for the deployment archive.
Stores UI5 and HTML5 apps and serves them through the approuter
CLI for the SAP BTP Application Frontend service
Binding onto hyperscaler object storage, chosen by plan
Cloud Foundry runtime of SAP BTP for polyglot applications
One inbox for tasks across SAP applications and BTP workflows