← Home

@openapitools/openapi-generator-cli

npm Repository Homepage
22
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

wing328ackintoshjimschubertkschecker

Keywords

rest-apirest-clientsdkgeneratorrestful-apiapiapi-clientapi-serveropenapi3openapioasrest

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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
install-scripts install-script:postinstall AI (install-scripts): opencollective funding prompt; benign and consistent across versions of this package. ai
semgrep semgrep:child-process-import AI (semgrep): Fires in bundled NestJS CLI binary; expected for this CLI tool's architecture. ai
phantom-deps phantom-dep:axios AI (phantom-deps): axios is a declared runtime dep used transitively via @nestjs/axios; stable false positive. ai
phantom-deps phantom-dep:reflect-metadata AI (phantom-deps): Known NestJS implicit runtime dependency; stable false positive for this package. ai
phantom-deps phantom-dep:@nuxtjs/opencollective AI (phantom-deps): Used by postinstall script; referenced in package.json collective config, not imported directly. ai

Versions (showing 22 of 22)

Version Deps Published
2.34.0 17 / 0
2.33.1 17 / 0
2.33.0 17 / 0
2.32.0 17 / 0
2.31.1 17 / 0
2.31.0 17 / 0
2.25.1 17 / 0
2.25.0 17 / 0
2.24.0 17 / 0
2.23.4 17 / 0
2.23.1 17 / 0
2.23.0 17 / 0
2.22.0 17 / 0
2.21.5 17 / 0
2.21.4 18 / 0
2.21.2 18 / 0
2.21.1 18 / 0
2.21.0 18 / 0
2.20.6 18 / 0
2.20.3 18 / 0
2.20.1 18 / 0
2.20.0 18 / 0

v2.34.0

1 finding
LOW No provenance attestation provenance

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

v2.33.1

1 finding
LOW No provenance attestation provenance

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

v2.33.0

1 finding
LOW No provenance attestation provenance

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

v2.32.0

1 finding
LOW No provenance attestation provenance

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

v2.31.1

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: opencollective || exit 0

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.31.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: opencollective || exit 0

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.25.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.25.0

1 finding
LOW No provenance attestation provenance

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

v2.24.0

1 finding
LOW No provenance attestation provenance

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

v2.23.4

1 finding
LOW No provenance attestation provenance

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

v2.23.1

1 finding
LOW No provenance attestation provenance

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

v2.23.0

1 finding
LOW No provenance attestation provenance

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

v2.22.0

1 finding
LOW No provenance attestation provenance

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

v2.21.5

1 finding
LOW No provenance attestation provenance

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

v2.21.4

1 finding
LOW No provenance attestation provenance

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

v2.21.2

1 finding
LOW No provenance attestation provenance

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

v2.21.1

1 finding
LOW No provenance attestation provenance

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

v2.21.0

1 finding
LOW No provenance attestation provenance

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

v2.20.6

1 finding
LOW No provenance attestation provenance

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

v2.20.3

1 finding
LOW No provenance attestation provenance

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

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