swagger-jsdoc
Generates swagger doc based on JSDoc
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:github-changes | AI (dependencies): Established changelog-generation tool, not malicious injection. | ai | |
| phantom-deps | phantom-dep:github-changes | AI (phantom-deps): Likely used in build/release tooling not scanned by import heuristic. | ai | |
| 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 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 6.3.0 | 6 / 15 | |
| 6.2.8 | 6 / 15 | |
| 6.2.7 | 6 / 15 | |
| 6.2.6 | 6 / 15 | |
| 6.2.5 | 6 / 15 | |
| 6.2.4 | 6 / 15 | |
| 6.2.3 | 6 / 15 | |
| 6.2.2 | 6 / 15 | |
| 6.2.1 | 6 / 15 | |
| 6.2.0 | 6 / 15 | |
| 6.1.0 | 6 / 15 | |
| 6.0.9 | 7 / 15 | |
| 6.0.8 | 5 / 15 | |
| 6.0.7 | 5 / 15 | |
| 6.0.6 | 5 / 15 | |
| 6.0.5 | 5 / 15 | |
| 6.0.4 | 5 / 15 | |
| 6.0.3 | 5 / 15 | |
| 6.0.2 | 5 / 15 | |
| 6.0.1 | 5 / 15 | |
| 6.0.0 | 5 / 15 |
v6.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.