GeneratorGeneratortypeCreates a project, a component or configuration once, when you run it, rather than taking part in every build.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

@rizing/cds-customer-stepbystep-tool

A tool that checks and completes the deployment configuration of a CAP project, written for Rizing's step-by-step CAP training, last released August 2023 from a repository since deleted.

Runs over a project root and applies the adjustments the training would otherwise have you make by hand, so the exercise is about what changed rather than about typing it.

Facts

Latestv1.2.0ReleasedLicenceISC

Where it sits

Lives in
Provides
DeploymentCAPDeploymentcapabilityGetting an application onto a runtime and keeping it there: build descriptors, deployment topology, service bindings and lifecycle operations. The target runtime determines how the application is packaged and configured.
Flavors
Node.jsJavafrom its runtime

Who is behind it

Rizing

Before choosing this

Conditions

PracticalFunctional boundary

Tied to a specific training repository and last released August 2023. 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.

LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2from DeploymentA productive CAP customer application is deployed using materials covered by this agreement.
  • § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
  • § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.

The CAP-specific agreement makes the deployment platform part of the permitted productive-use condition, so deployment choices need the applicable agreement checked rather than treated as purely technical.

SAP Developer License Agreement 3.2 CAP →

What it declares

Every artifact

Type
Generator
Origin
Independently maintained
Runtime
build time

As a generator

Generates
does not say
Run with
does not say
Distributed through
does not say

Connections1

@rizing/cds-customer-stepbystep-tool connections@rizing/cds-customer-stepbystep-toolPROVIDES→ provides1provides authoredDeployment

Install

npm add @rizing/cds-customer-stepbystep-tool

Derived from the package name. No recipe recorded; the README has the configuration.

History

Latest

v1.2.0

  1. v1.1.2

  2. v1.1.1

  3. v1.1.0

  4. v1.0.3

  5. v1.0.2

  6. v1.0.1

  7. v1.0.0

On npm
0downloads per week, npm
Weekly downloads for @rizing/cds-customer-stepbystep-tool26 complete calendar weeks from 2026-04-27 to 2026-10-25; the latest total is 0.27 Apr – 3 May: 164 May – 10 May: 2011 May – 17 May: 1618 May – 24 May: 925 May – 31 May: 41 Jun – 7 Jun: 238 Jun – 14 Jun: 3815 Jun – 21 Jun: 822 Jun – 28 Jun: 1129 Jun – 5 Jul: 136 Jul – 12 Jul: 1213 Jul – 19 Jul: 320 Jul – 26 Jul: 927 Jul – 2 Aug: 23 Aug – 9 Aug: 1710 Aug – 16 Aug: 1017 Aug – 23 Aug: 424 Aug – 30 Aug: 931 Aug – 6 Sept: 37 Sept – 13 Sept: 814 Sept – 20 Sept: 621 Sept – 27 Sept: 328 Sept – 4 Oct: 45 Oct – 11 Oct: 212 Oct – 18 Oct: 319 Oct – 25 Oct: 0
Deployment
  1. @cap-js/cap-operator-pluginGenerates Helm charts for the CAP Operator on Kubernetes
  2. @sap/cds-dkCommand line client and development toolkit for CAP

Details

Sources2
npm registrydiscovered here, keywords:cdschecked
npm registry, @rizing/cds-customer-stepbystep-toolversion, releases, installschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesbuild-time
latestv1.2.0
first release
releases and cadence8, ~0d median
discovered vianpm registry · keywords:cds
first seen in the atlas
ecosystem and domaincap, operations-and-runtime
History in the atlas2
  1. 404 from the GitHub API. Found by the first full run of scripts/check-links.mjs — the citation had a checked date and nobody had re-read it.
  2. First seen.
For your agent
Ref
artifact:rizing-cds-customer-stepbystep-tool
JSON
/artifacts/rizing-cds-customer-stepbystep-tool.json
MCP
Connecting an agent