Everything in CAP
Type
Domain: Developer Experience
Origin: Not from SAP
Signals
More: 2
Group by: Capability
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.
CAP project built and deployed to Cloud Foundry by GitHub Actions
Consumer side of a CAP Java parent pom promotion model with Renovate
Neither the package manifest nor the repository tree declares a licence.
Maven parent pom pinning cds-services-bom and Spring Boot for CAP Java
Neither the package manifest nor the repository tree declares a licence.
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
CLI starting several CAP services and an AppRouter locally together
Serves a Vite app through cds watch and imports .cds files
CAP Java service consuming a Business Partner API mocked in Node.js
Neither the package manifest nor the repository tree declares a licence.
Ten short CAP Java references, one document per topic
CAP project simulating S/4HANA Private Edition OData APIs locally
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 28 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.
Ten short CAP Java references, one document per topic
Convention-based handler layer for CAP with draft lifecycle hooks
Typed class-based service layer over CAP ApplicationService
Last released July 2022, and no repository is declared on the package.
One handler file per entity in CAP services
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.
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.
CAP service in TypeScript using types from @cap-js/cds-typer