Everything in CAP / Node.js
Type
Domain: Developer Experience
Origin: 2
Signals
Node.js: Answers in Node.js
More
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
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
Interactive generator for CAP event handler files
Interactive project installer for CAP Node.js
Shared ESLint configuration for SAPUI5 and CAP projects
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.
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.
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.
CAP project simulating S/4HANA Private Edition OData APIs locally
pnpm workspace running CAP, a local launchpad and two UI5 apps
Neither the package manifest nor the repository tree declares a licence.
AWK script sketching an ER diagram from .cds files
No published releases; repository quiet for 26 months.
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.
Fills db/data with relationally consistent CSV from a .cds schema
Sandbox launchpad for all SAPUI5 apps in a CAP workspace
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
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
CDS build task compiling TypeScript sources during cds build
Decorator-based routing of CAP service handlers in TypeScript
Release and repository quiet for 46 months.
CLI generating TypeScript interfaces from a CDS model
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
Placeholder package under a CAP annotations name, no annotations
The manifest calls it a dummy library exposing custom CDS annotations, but the published contents are a one-line README, a single exported barrier() whose body is throw Error("not yet implemented"), and no .cds file at all — there is nothing to import and nothing to annotate with. No repository, one release, May 2025.