← Home

swagger-jsdoc

npm Repository Homepage

Generates swagger doc based on JSDoc

2
Versions
MIT
License
No
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

chdanielmuellersibeliuskalin.chernev

Keywords

swaggeropenapijsdoc

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is used to load user-specified swagger definition files — a core feature of this tool, not an arbitrary code execution risk. ai
dependencies unvetted-dep:swagger-parser AI (dependencies): swagger-parser is a legitimate OpenAPI validation library; its use is expected and appropriate for swagger-jsdoc's purpose. ai

Versions (showing 2 of 2)

Version Deps Published
6.3.0 6 / 15
6.2.8 6 / 15

v6.3.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: kalin.chernev → chdanielmueller (on 2026-05-22, known maintainer) provenance

This version was published by a different npm account (chdanielmueller) than the most recent previously approved version (kalin.chernev) on 2026-05-22, but chdanielmueller 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.

v6.2.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.