@ibm-cloud/watsonx-ai — Greenflagged

IBM watsonx.ai Node.js SDK

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

ricelliscloudant-sdks-automationsecrets.automationnvenkateshdpittner_ibmexternaluse.sqlqueryibm-reggieibm-devx-sdkibm-cloud-event-notificationsreggeenridsorgwxai-sdk-automationschmaticcodeengine-ui-teamstephaniegalang-ibmmdarmawanrajan.gahlout1pyrookajeremy-johnson-ibm

Keywords

ibmwatsonxwatsonx-ai

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): IBM corporate SDK with documented team rotation; new maintainers have IBM-affiliated usernames consistent with legitimate team changes.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of kpnode alongside IBM-affiliated additions is consistent with normal IBM team rotation, not a hostile takeover.	ai	2026/04/23
phantom-deps	phantom-dep:ts-node	AI (phantom-deps): ts-node is a standard TypeScript toolchain dependency referenced in config files; expected for a TypeScript SDK project.	ai	2026/04/23
phantom-deps	phantom-dep:extend	AI (phantom-deps): extend is a standard utility used in IBM SDK core patterns; phantom usage is expected in this SDK context.	ai	2026/04/23
phantom-deps	phantom-dep:@types/node	AI (phantom-deps): @types/node is a framework-scoped type package loaded by convention in TypeScript projects; not a real phantom dep concern.	ai	2026/04/23

Versions (showing 42 of 42)

Version	Deps	Published
1.7.11	5 / 0	2026-04-01
1.7.10	5 / 0	2026-03-18
1.7.9	4 / 0	2026-03-04
1.7.8	4 / 0	2026-02-18
1.7.7	4 / 0	2026-01-23
1.7.6	4 / 0	2026-01-08
1.7.5	4 / 0	2025-12-08
1.7.4	4 / 0	2025-11-21
1.7.3	4 / 0	2025-11-12
1.7.2	4 / 0	2025-10-29
1.7.1	4 / 0	2025-10-28
1.7.0	4 / 0	2025-10-13
1.6.13	4 / 21	2025-09-17
1.6.12	4 / 21	2025-08-28
1.6.11	3 / 21	2025-08-25
1.6.10	3 / 21	2025-07-28
1.6.9	3 / 21	2025-07-23
1.6.8	3 / 21	2025-06-20
1.6.7	3 / 21	2025-05-28
1.6.6	3 / 21	2025-05-20
1.6.5	3 / 21	2025-05-12
1.6.4	4 / 20	2025-03-28
1.6.3	4 / 20	2025-03-27
1.6.2	4 / 20	2025-03-27
1.6.1	4 / 20	2025-03-24
1.6.0	4 / 20	2025-03-14
1.5.1	4 / 20	2025-02-28
1.5.0	4 / 20	2025-02-11
1.4.0	4 / 20	2025-01-29
1.3.2	4 / 20	2025-01-20
1.3.1	3 / 20	2025-01-07
1.3.0	3 / 20	2024-12-03
1.2.0	3 / 20	2024-11-27
1.1.3	3 / 23	2024-11-15
1.1.2	3 / 23	2024-10-30
1.1.1	3 / 23	2024-10-17
1.1.0	3 / 22	2024-10-08
1.0.2	3 / 22	2024-09-25
1.0.1	3 / 22	2024-08-08
1.0.0	3 / 22	2024-08-07
0.1.1	3 / 22	2024-06-19
0.1.0	3 / 22	2024-06-19

v1.7.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.5

3 findings

HIGH New obfuscated file: types/index.d.mts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: types/index.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.4

3 findings

HIGH New obfuscated file: types/index.d.mts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: types/index.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.