Skip to content

docs: fix unscoped npx generate-odata-client command in documentation - #2632

Merged
betinacosta merged 3 commits into
mainfrom
docs/unsafe-npx-generate-odata-client-docs
Oct 26, 2026
Merged

betinacosta merged 3 commits into
mainfrom
docs/unsafe-npx-generate-odata-client-docs

Conversation

@betinacosta

Copy link
Copy Markdown
Member

The generator documentation referenced npx generate-odata-client without a package scope. Since generate-odata-client is not registered under the SAP org on npm, this bare name resolves from the public registry — meaning developers (and AI coding agents following the docs) could silently install and execute an uncontrolled third-party package.

Fix: Replace the bare npx generate-odata-client invocation with the scoped npx @sap-cloud-sdk/generator generate-odata-client, which resolves to the package SAP owns and publishes.

Impact: Any developer or AI coding agent following the documented steps verbatim was at risk of running arbitrary code from the public registry. No changes to the package itself or its behavior — documentation only.

@betinacosta
betinacosta merged commit 00bfe6e into main Oct 26, 2026
6 checks passed
@betinacosta
betinacosta deleted the docs/unsafe-npx-generate-odata-client-docs branch October 26, 2026 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants