@openapitools/openapi-generator-cli No license 51 versions

@openapitools/openapi-generator-cli

npm Repository Homepage

51

Versions

—

License

Yes

Install Scripts

Missing

Provenance

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

wing328ackintoshjimschubertkschecker

Keywords

rest-apirest-clientsdkgeneratorrestful-apiapiapi-clientapi-serveropenapi3openapioasrest

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file-transition:main.js	AI (source-diff): main.js is webpack bundle output (webpackBootstrap), not obfuscation; stable for this build tool.	ai	2026/07/22
publish-pattern	dormant-publish	AI (publish-pattern): Established OpenAPITools org package; long gap between releases is plausible for a stable CLI wrapper, no suspicious changes in diff.	ai	2026/04/30
phantom-deps	phantom-dep:axios	AI (phantom-deps): axios is a declared runtime dep used transitively via @nestjs/axios; stable false positive.	ai	2026/04/28
install-scripts	install-script:postinstall	AI (install-scripts): opencollective funding prompt; benign and consistent across versions of this package.	ai	2026/04/28
phantom-deps	phantom-dep:@nuxtjs/opencollective	AI (phantom-deps): Used by postinstall script; referenced in package.json collective config, not imported directly.	ai	2026/04/28
phantom-deps	phantom-dep:reflect-metadata	AI (phantom-deps): Known NestJS implicit runtime dependency; stable false positive for this package.	ai	2026/04/28
semgrep	semgrep:child-process-import	AI (semgrep): Fires in bundled NestJS CLI binary; expected for this CLI tool's architecture.	ai	2026/04/28

Versions (showing 51 of 70)

View all versions

Version	Deps	Published
2.34.0	17 / 0	2026-05-20
2.33.1	17 / 0	2026-05-19
2.33.0	17 / 0	2026-05-19
2.32.0	17 / 0	2026-04-28
2.31.1	17 / 0	2026-04-07
2.31.0	17 / 0	2026-03-24
2.27.0	17 / 0	2025-12-30
2.25.1	17 / 0	2025-11-18
2.25.0	17 / 0	2025-10-12
2.24.0	17 / 0	2025-09-28
2.23.4	17 / 0	2025-09-16
2.23.1	17 / 0	2025-08-25
2.23.0	17 / 0	2025-08-22
2.22.0	17 / 0	2025-08-12
2.21.5	17 / 0	2025-08-12
2.21.4	18 / 0	2025-07-23
2.21.2	18 / 0	2025-07-16
2.21.1	18 / 0	2025-07-15
2.21.0	18 / 0	2025-06-25
2.20.6	18 / 0	2025-06-25
2.20.3	18 / 0	2025-06-24
2.20.1	18 / 0	2025-05-19
2.20.0	18 / 0	2025-04-27
2.19.1	18 / 0	2025-04-17
2.19.0	18 / 0	2025-04-16
2.18.4	18 / 0	2025-03-15
2.18.3	18 / 0	2025-03-14
2.18.2	18 / 0	2025-03-14
2.17.0	18 / 0	2025-02-28
2.16.3	18 / 0	2025-01-26
2.16.2	18 / 0	2025-01-22
2.16.1	18 / 0	2025-01-22
2.16.0	18 / 0	2025-01-22
2.15.4	18 / 0	2025-01-22
2.15.1	18 / 0	2024-11-01
2.15.0	18 / 0	2024-10-25
2.14.1	18 / 0	2024-10-21
2.13.13	18 / 0	2024-10-03
2.13.12	18 / 0	2024-09-28
2.13.10	18 / 0	2024-09-28
2.13.8	18 / 0	2024-09-22
2.13.7	18 / 0	2024-09-18
2.13.6	18 / 0	2024-09-18
2.13.5	18 / 0	2024-08-20
2.13.1	17 / 0	2024-03-19
2.10.1	17 / 0	2024-03-06
2.7.0	16 / 0	2023-07-18
2.4.23	15 / 0	2021-12-28
2.4.19	15 / 0	2021-12-17
2.4.12	15 / 0	2021-10-06
2.4.9	15 / 0	2021-10-02

v2.27.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: kschecker → wing328 (on 2025-12-30, known maintainer) provenance

This version was published by a different npm account (wing328) than the most recent previously approved version (kschecker) on 2025-12-30, but wing328 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.19.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.

v2.19.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.

v2.18.4

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.

v2.18.3

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.

v2.18.2

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.

v2.17.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.

v2.16.3

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.

v2.16.2

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.

v2.16.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.

v2.16.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.

v2.15.4

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.

v2.15.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.

v2.15.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.

v2.14.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.

v2.13.13

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.

v2.13.12

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.

v2.13.10

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.

v2.13.8

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.

v2.13.7

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.

v2.13.6

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.

v2.13.5

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.

v2.13.1

2 findings

HIGH Modified file became obfuscated: main.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

LOW No provenance attestation provenance

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

v2.10.1

2 findings

HIGH Modified file became obfuscated: main.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

LOW No provenance attestation provenance

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

v2.7.0

2 findings

HIGH Modified file became obfuscated: main.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

LOW No provenance attestation provenance

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

v2.4.23

2 findings

HIGH Modified file became obfuscated: main.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

LOW No provenance attestation provenance

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

v2.4.19

2 findings

HIGH Modified file became obfuscated: main.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

LOW No provenance attestation provenance

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

v2.4.12

2 findings

HIGH Modified file became obfuscated: main.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

LOW No provenance attestation provenance

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

v2.4.9

2 findings

HIGH Modified file became obfuscated: main.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

LOW No provenance attestation provenance

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