Everything in CAP
Type: 3
Domain
Origin
Signals
More: MIT
Group by: Capability
Where it runs
Distributed through
Form
CLI for DROP and RENAME schema changes beside @cap-js/postgres
Fork of cds-dbm with deploy, load, diff and drop tasks
Release and repository quiet for 39 months.
Node module for CAP calling external APIs through a destination
Quiet Release and repository quiet for 57 months.
Functional boundary The package declares `@sap/cds` ^4.5.2 among its dependencies and pins `@sap-cloud-sdk/core` at 1.37.1, so a project on CAP 5 or later is outside the range it states.
Destination resolution and axios calls from CAP configuration
Release and repository quiet for 46 months.
MTA deploying CAP, HDI container and a Fiori elements app
Deep Agents filesystem over an SAP Document Management repository
Not a way to edit Office formats: the author states that access to a file does not automatically provide native editing of Word documents, spreadsheets or PDFs, and suggests starting with text-based content such as instructions, templates and reports. Not a control point either: a prompt telling the agent to ask for confirmation or to leave a template alone needs enforceable application controls where that is a business requirement, and the host application stays responsible for the authenticated request context and tenant isolation.
Toolkit turning a CAP service into tools for agent frameworks
LangChain vector store on SAP AI Core Document Grounding
LangChain vector store with CDS entities for embeddings
Toolkit turning a CAP service into tools for agent frameworks
Authenticating a CAP service against Azure AD B2C
Utility bundle for CAP handlers: builder, roles, validation, queries
It is a bundle rather than a plugin with one job, and a single release from March 2026 — depending on it for the query helpers brings the auth and validation layers too.
Utility bundle for CAP handlers: builder, roles, validation, queries
It is a bundle rather than a plugin with one job, and a single release from March 2026 — depending on it for the query helpers brings the auth and validation layers too.
Zod schemas as CAP validation middleware
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.
MTA deploying CAP, HDI container and a Fiori elements app
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.
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
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.
CAP project simulating S/4HANA Private Edition OData APIs locally
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
Decorator-driven handler registration for CAP in TypeScript
Typed BaseRepository over CAP entities
Decorator-based routing of CAP service handlers in TypeScript
Release and repository quiet for 46 months.
CLI generating TypeScript interfaces from a CDS model
MTA deploying CAP, HDI container and a Fiori elements app
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.
CAP agent writing reports into a shared SDM document workspace