Everything in CAP / Node.js
Type: 2
Domain
Origin
Signals
Node.js: Does not say
More
Group by: Capability
Where it runs
Distributed through
SAP's Node.js driver for SAP HANA
Developer-centric command line for SAP HANA
Destination lookup and connectivity proxy for the Cloud SDK
HTTP client carrying a destination's credentials
Shared machinery under the Cloud SDK's OData and OpenAPI clients
Generated OpenAPI clients for the Cloud SDK
Timeouts, retries and circuit breaking around remote calls
General utilities shared across the Cloud SDK packages
Prebuilt SAP S/4HANA integration package for CAP projects
Prebuilt SAP S/4HANA integration package for CAP projects
Developer-centric command line for SAP HANA
CLI for Joule digital assistants and Joule Studio solutions
Pro-code CLI for building and deploying Joule Studio solutions
Orchestration Service client for templating, grounding and masking
Orchestration Service client for templating, grounding and masking
Vercel AI SDK provider for SAP AI Core
AI Core control plane API surface of SAP's AI SDK
Shared internals of SAP's AI SDK
Client for foundation models via SAP AI Core and Generative AI Hub
Orchestration Service client for templating, grounding and masking
Client for prompts kept in SAP's prompt registry
Orchestration Service client for templating, grounding and masking
Client for prompts kept in SAP's prompt registry
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.
Library for sending usage telemetry data
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.
Language server for CDS
Command line for changing features of an existing Fiori project
Writer of flexible programming model elements into Fiori elements apps
Shared functions and types of the Fiori generators
Writer that adds an OData service to an existing UI5 project
Fiori Elements mock server plugin taking a CDS file as metadata
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.
Parser for annotations in CDS source
Converter from CDS annotations to their OData form
Programmatic API for reading and writing project annotations
OASIS and SAP OData vocabularies with a VocabularyService
Reader and writer for i18n bundles of UI5 or CAP projects
Fiori documentation indexed as embeddings