Everything in CAP / Node.js
Type
Domain
Origin
Signals
Content
Node.js: Answers in Node.js
More
Group by: Ecosystem
UI5 frontend performance and error capture for CAP
User details and quickview links for createdBy and modifiedBy
npx tool adding worked example files to a CAP project
Last released April 2024.
Agent skills for CAP development, each a SKILL.md with references
Custom messages and handler classes for CAP input validation
Toolkit turning a CAP service into tools for agent frameworks
Azure AD and Azure AD B2C authentication strategy for CAP
Last released January 2022 at 0.0.21, against a passport strategy Microsoft has since deprecated.
CAP caching plugin for query results and remote service responses
When user-dependent responses are cached without user-aware or explicit operation keys, or translated responses share keys across locales. These cases require key isolation; locale-aware keys are off by default.
JWT authentication for CAP without xsuaa or xssec
Last released April 2022 at 0.0.2, and no repository is declared on the package.
Gherkin scenarios driving a running CAP service
Data federation for CAP via delegation, caching and replication
Scheduled READ, MAP, WRITE pipelines between CAP services
Delta deployment and migrations for CAP database adapters
Archived The declared repository is archived.
Functional boundary The repository is archived, so nothing here will move again. Fine to keep where it already runs; anything new should start from what the current cds deploy leaves open rather than from this.
Maps Microsoft Entra ID groups and app roles onto cds.User roles
Quiet Release and repository quiet for 25 months.
Functional boundary It performs no authentication flow of its own. The app must already be protected by Entra ID OAuth 2.0 at the App Service level; this only maps the resulting claims. It is explicitly not intended to run locally.
Captures CAP service errors, deduplicates them and mails alerts
Alerting by mail is not telemetry — if you need traces and metrics correlated across handlers, that is a different layer. It also publishes no repository, so the package is the only thing to read.
Stores, browses and resends messages a CAP service receives
Feature-toggle pattern for CAP CDS
Last released June 2022 at 0.0.6, and no repository is declared on the package.
CAP-to-CAP data federation over SAP HANA synonyms
When your adoption policy excludes experimental dependencies: the [maintainer’s README](https://github.com/cap-js/cds-federation-synonyms#about-this-project) explicitly labels this plugin experimental.
Typed class-based service layer over CAP ApplicationService
Last released July 2022, and no repository is declared on the package.
Reusable internals for authors of CAP extensions
Explicitly internal utilities, so the surface is not a stable public API and last moved in March 2024. 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.
Kafka adapter exposing topics as a CDS messaging service
Sandbox launchpad for all SAPUI5 apps in a CAP workspace
MongoDB as a CAP database service through Mongoose
It declares no peer range on [@sap/cds](artifact:sap-cds) and publishes no repository, so there is nothing to read but the package itself and no CI to look at.
MySQL and MariaDB database adapter for CAP
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.
NATS messaging service for the CAP Node.js runtime
Last released December 2022. Nothing says it fails on current cds, but nothing says it was tried either. 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.
Fills a CDS element from a database-backed number range
PostgreSQL adapter for SAP CDS from the SAP Mentors community
The declared repository is archived.
One handler file per entity in CAP services
CDS build task compiling TypeScript sources during cds build
UI5 CLI middlewares running inside the CDS server
For a deployed application's UI. The README adds it with `npm add cds-plugin-ui5 -D`, a development dependency of the CDS server, and states nothing about a build or a deployment.
Rate-limit pattern for CAP Node.js applications
Last released January 2024 at 0.0.6. 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.
Decorator-based routing of CAP service handlers in TypeScript
Release and repository quiet for 46 months.
CAP plugin turning DELETE into a flag on annotated entities
It changes what DELETE means for every client of the annotated projection, so anything that must actually remove a row — an erasure request, a retention job — has to go around it.
Spreadsheet upload into a CDS entity, parsed on the server
Swagger UI for a CAP service's OpenAPI definition
TextMate grammar for the CDS language
Not an editor integration. If you want completion, navigation and diagnostics, that is the CDS language server, not this.
Zod schemas as CAP validation middleware
CLI generating TypeScript interfaces from a CDS model
Destination resolution and axios calls from CAP configuration
Release and repository quiet for 46 months.
CDS plugin for OData change tracking in CAP applications
CAP plugin joining external entities with internal tables at query
The declared repository is on SAP's internal GitHub (github.tools.sap) and is not publicly reachable, so npm is the only place to read anything about it.
ESLint rules flagging deprecated CAP configuration
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.
MCP server searching seventeen SAP documentation repositories
It reads documentation, never a system: nothing in it opens a package.json, a CDS model or an ABAP client, so a question about what your own project does has to be answered elsewhere. The offline half is only as fresh as the submodules the last build pinned, and the index answers where something is written down rather than which of two packages fits a task.
SDK-free TypeScript client for SAP synchronous RFC on Node.js
The maintainer states 0.x is beta with no production SLA, and scopes support deliberately narrowly: direct application-server transport, classic serialization and password authentication on S/4HANA 2023 and NetWeaver 7.50. Anything outside that is untested rather than unsupported.
OpenTelemetry support for the CDS Node.js runtime
CAP agent writing reports into a shared SDM document workspace
Attaches a debugger to a CAP app running on Cloud Foundry
CAP Node.js plugin mapping CDS entities to SAP Document Management
Archived The declared repository is archived.
Functional boundary For versioned or thumbnail-enabled repositories, or bulk upload and download, the [README](https://raw.githubusercontent.com/vneecious/sap-cap-sdm-plugin/d9f036b16542e5c5b9b6dc704e0ba5f880193212/README.md) labels this an “early release” and lists those features as unsupported.
CAP plugin validating input against @Validator JSON Schema rules
Quiet Release and repository quiet for 30 months.
Functional boundary The annotation sits on a single element, so a rule that spans two fields, or one that needs a lookup, has nowhere in it to go.
AWK script sketching an ER diagram from .cds files
No published releases; repository quiet for 26 months.
Terminal UI running Bruno collections against a CAP service
CAP and SAPUI5 demo of recovery from a supply disruption
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The data is illustrative: availability is binary and backup capacity unlimited, and the model carries no inventory; nothing in it is forecast or priced. The recall half runs only against classic ABAP, because its openCypher trace goes through ADBC, which is not released for ABAP Cloud, and it expects an SSH tunnel to the A4H system it was built against. A plain `npm start` passes no model key, so the agent cannot be used on a server started that way.
CDS plugin and UI5 controls for AI text features via SAP AI Core
It is text processing, not an agent: there is no tool calling, no retrieval and no conversation. It needs SAP AI Core, and the backend half needs [@sap-ai-sdk/orchestration](artifact:sap-ai-sdk-orchestration) installed alongside it — an optional peer, so a frontend-only install stays lean.
Demo CAP bookshop with server-rendered UI5 views
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary As a deployment template it stops at the service: the `mta.yaml` has one module, `gen/srv` on the Node.js buildpack, and no HTML5 repository or router module for the app.
CAP plugin rendering UI5 views with entity data on the server
On the UI5 path what comes back is an XML view or fragment with the data already substituted, streamed as the entity's media content, rather than an HTML page — the README calls this pre-rendering, and only the Vue path produces markup. The view kept under `srv/` has its UI5 bindings replaced by Handlebars expressions, so it is a second copy of the view, separate from the one the application ships. Version 1.0.8 declares `@sap/cds` `>=8` as its peer dependency, which puts a project on CAP 7 outside its stated range.
CDS vocabulary for User-Rendered Patterns display annotations
The declared repository is github.com/your-username/urp-vocab, an unedited placeholder. Three releases, September 2025.
Serves a Vite app through cds watch and imports .cds files
MTA deploying CAP, HDI container and a Fiori elements app
Chat app on CAP and SAPUI5 against the OpenAI API
It calls the OpenAI API directly with a key in the environment. It was written in early 2023 and last touched in May 2023, which is before SAP AI Core and the CAP LLM plugins existed — so read it for the shape of the application, not for how a CAP service should reach a model today.
VECTOR_EMBEDDING in a CDS entity for FAQ similarity search
Neither the package manifest nor the repository tree declares a licence.
Local chat client for SAP questions with a CAP LangGraph backend
Neither the package manifest nor the repository tree declares a licence.
List report inline edit on a draft-enabled CAP service
Neither the package manifest nor the repository tree declares a licence.
Outbound navigation patterns from a Fiori Elements list report
Neither the package manifest nor the repository tree declares a licence.
CAP project simulating S/4HANA Private Edition OData APIs locally
CAP samples calling SAP AI Core through the SAP Cloud SDK for AI
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples comparing SAP AI Core responses with content filtering
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples generating email through SAP AI Core with anonymization
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples using SAP AI Core's Prompt Registry for templates
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples filling a prompt template sent to SAP AI Core
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples embedding CSV rows into the SAP HANA Cloud vector store
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples running RAG similarity queries over SAP HANA Cloud vectors
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP service reading and writing MongoDB from custom handlers
Neither the package manifest nor the repository tree declares a licence.
CAP sample of SAP Event Mesh events feeding a multi-tenant SaaS app
OWASP Top 10 workshop exploiting and fixing flaws in a CAP Node.js app
Financial Risk Analyzer built by an agent grounded in SAP MCP servers
Five-part workshop on CDS, from a first service to constraints
CodeJam building a full-stack CAP app on SAP HANA Cloud
reCAP 2025 workshop on CAP's local-development toolset
CodeJam on consuming external services from a CAP project
Travel-booking reference app on CAP Node.js and Java backends
CAP data model of many-to-many relationships on a Star Wars dataset
CAP-based PWA for EV drivers proxying SAP E-Mobility OData APIs
CodeJam building a bookshop app on the flexible programming model
CAP Node.js server behind the OData Deep Dive tutorials
Event registration app showing OData V4 draft with UI5 and CAP
CAP Risks and Mitigations project with a Spreadsheet Upload button
TechEd 2025 workshop on OWASP Top 10 risks in CAP applications
Product-review screen consuming ui5-cap-ai-features on CAP
Neither the package manifest nor the repository tree declares a licence.
UI5 apps calling CAP OData actions and functions from custom code
Neither the package manifest nor the repository tree declares a licence.
Todo app with CAP and SAPUI5 in TypeScript over OData V4
Neither the package manifest nor the repository tree declares a licence.
Command line for changing features of an existing Fiori project
Writer of flexible programming model elements into Fiori elements apps
MCP server for creating and editing Fiori applications
Reader and writer for i18n bundles of UI5 or CAP projects
Writer that adds an OData service to an existing UI5 project
OASIS and SAP OData vocabularies with a VocabularyService
MCP server for UI5 development with ten tools
It reads a UI5 project and the framework's own documentation, not a running system or a backend: a question about the service behind the app is answered somewhere else. Node.js v20.17 or v22.9 and above.
UI5 app consuming the cds-bookshop server via ui5-middleware-cap
pnpm workspace running CAP, a local launchpad and two UI5 apps
Neither the package manifest nor the repository tree declares a licence.
Versioned specification of the abap2UI5 roundtrip protocol
Neither suite has been run against an ABAP system: the reference backends are the framework transpiled to Node and cap2UI5 on CAP, so what a check does on a real system is open. The portable profile is a subset of 61 controls, filled from a census of 247 core apps of which 64.8 % run unchanged, so an app outside it renders placeholders in the terminal and Adaptive Cards renderers.
Hosted workspace redrawing custom ABAP as BPMN and grading it
Not reachable Not reachable since 2026-10-20.
Functional boundary The Level A–D grade merges SAP's two published files in the tool's own engine: it is an orientation rather than an ATC result and is left out of the signed audit pack, and the repository documents state by state where the grade is expected to differ from what the clean core ATC check reports. Nothing here runs ABAP Unit — on the RAP track that result is recorded from your own SAP system, and generated CAP tests run against mocks in an isolated runner rather than in a real SAP S/4HANA system. Tenants, organisation accounts, single sign-on, a self-hosted edition and write access through an API are deliberately not built, and one account has five analysis runs before a Gemini API key of its own is needed.
SAP's Node.js driver for SAP HANA
CLI for Joule digital assistants and Joule Studio solutions
Pro-code CLI for building and deploying Joule Studio solutions
API proxies with security and traffic policies and Developer Hub
Identity Authentication and Identity Provisioning as one tenant
Managed queues and topics over AMQP, MQTT and REST
Low-code SAP Build capability for custom Joule skills and agents
Binding onto hyperscaler object storage, chosen by plan
Managed PostgreSQL from the hyperscaler via a BTP service binding
Managed Redis from the hyperscaler via a BTP service binding
AI runtime on BTP with the Generative AI Hub
Skill assessing API usage against the SAP API Policy
It says so itself, in bold, and the atlas repeats it: not legal advice and not a compliance decision. Only SAP, your contract, or SAP support can answer bindingly, and the skill routes legal, commercial and roadmap questions there rather than guessing at them. Treat the output as evidence gathered, not as a verdict.
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.
Collects Cloud Foundry or Kyma logs into a searchable Kibana
Ingests and retains compliance audit data from BTP
OAuth server issuing JWTs and holding scopes for BTP apps
Cloud Foundry runtime of SAP BTP for polyglot applications
Development environment on BTP for UI5, Fiori, mobile and CAP
Proxy from cloud apps to on-premise systems via Cloud Connector
Predefined CI/CD pipelines for SAP development projects
Vault for an application's passwords, keys and keyrings
Named, credentialed addresses of other systems resolved at runtime
Extracts header fields and line items from business documents
APIs and a UI5 component for document management in apps
Boolean and string flags read by applications at runtime
SAP's relational database platform, on-premise and in HANA Cloud
For provisioning a managed database on BTP, see [SAP HANA Cloud](artifact:btp-hana-cloud). Features differ between HANA versions; an on-premise deployment and a cloud instance are not interchangeable without compatibility checks.
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.
Stores UI5 and HTML5 apps and serves them through the approuter
Event streaming and management platform in Integration Suite
Calls an application endpoint on a schedule and logs each run
SAP's AI engagement layer across SAP applications
Scans uploaded files over REST with ClamAV
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.
Registers a multitenant application for subaccount subscriptions
One inbox for tasks across SAP applications and BTP workflows
Developer-centric command line for SAP HANA
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.
Agent skill for SAP Customer Experience APIs, CDS and errors
SAP's managed environment for building custom agents and workflows
Hosted MCP server of developers.sap.com tutorials and missions
Local desktop workspace for AI conversations with SAP connectors
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.
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.
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.
