Everything in CAP
Type: 2
Domain
Origin
Signals
More: 2
Group by: Capability
Distributed through
Generates
Run with
Command line client and development toolkit for CAP
Developer-centric command line for SAP HANA
Command line client and development toolkit for CAP
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
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.
Generates Helm charts for the CAP Operator on Kubernetes
Command line client and development toolkit for CAP
CLI for operating tenants of multitenant CAP applications
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.
Command line client and development toolkit for CAP
Command line for changing features of an existing Fiori project
Command line client and development toolkit for CAP
Maven archetype generating a new CAP Java project
CLI starting several CAP services and an AppRouter locally together
Command line client and development toolkit for CAP
Command line client and development toolkit for CAP
Command line client and development toolkit for CAP
Compares a CAP project's CSV data with its database rows
CSV seed data generated from @Mockdata annotations with Faker
Quiet Release and repository quiet for 27 months.
Functional boundary Not a test-data factory. It writes files at build time to seed a database, so it does not build fixtures inside a unit test. The declared peer range stops at cds 7 — nothing says it fails on 9, but nothing says it was tried either.
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.
CLI for the SAP BTP Application Frontend service