jsdoc-api
A programmatic interface for 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): jsdoc-api's core purpose is to invoke jsdoc as a subprocess; child_process usage is fundamental and expected across all versions. | ai |
Versions (showing 58 of 58)
| Version | Deps | Published |
|---|---|---|
| 9.3.6 | 7 / 0 | |
| 9.3.5 | 7 / 0 | |
| 9.3.4 | 7 / 0 | |
| 9.3.3 | 7 / 0 | |
| 9.3.2 | 7 / 0 | |
| 9.3.1 | 7 / 0 | |
| 9.3.0 | 7 / 0 | |
| 9.2.0 | 7 / 0 | |
| 9.1.0 | 7 / 0 | |
| 9.0.2 | 7 / 0 | |
| 9.0.1 | 7 / 0 | |
| 9.0.0 | 7 / 0 | |
| 8.1.1 | 9 / 4 | |
| 8.1.0 | 8 / 4 | |
| 8.0.0 | 9 / 5 | |
| 7.2.0 | 9 / 5 | |
| 7.1.1 | 9 / 5 | |
| 7.1.0 | 9 / 5 | |
| 7.0.1 | 9 / 6 | |
| 7.0.0 | 9 / 6 | |
| 6.0.0 | 9 / 6 | |
| 5.0.4 | 9 / 6 | |
| 5.0.3 | 9 / 6 | |
| 5.0.2 | 9 / 6 | |
| 5.0.1 | 9 / 5 | |
| 4.0.3 | 9 / 5 | |
| 4.0.2 | 9 / 5 | |
| 4.0.1 | 9 / 5 | |
| 4.0.0 | 9 / 5 | |
| 3.0.0 | 9 / 5 | |
| 2.0.6 | 11 / 7 | |
| 2.0.5 | 11 / 7 | |
| 2.0.4 | 11 / 7 | |
| 2.0.3 | 12 / 7 | |
| 2.0.2 | 12 / 7 | |
| 2.0.1 | 12 / 7 | |
| 2.0.0 | 12 / 7 | |
| 1.2.4 | 12 / 7 | |
| 1.2.3 | 12 / 7 | |
| 1.2.2 | 12 / 7 | |
| 1.2.1 | 12 / 7 | |
| 1.2.0 | 12 / 6 | |
| 1.1.0 | 11 / 6 | |
| 1.0.5 | 12 / 6 | |
| 1.0.4 | 12 / 6 | |
| 1.0.3 | 12 / 6 | |
| 1.0.2 | 12 / 6 | |
| 1.0.1 | 12 / 6 | |
| 1.0.0 | 12 / 6 | |
| 0.4.1 | 12 / 6 | |
| 0.4.0 | 12 / 6 | |
| 0.3.0 | 10 / 6 | |
| 0.2.2 | 10 / 6 | |
| 0.2.1 | 9 / 6 | |
| 0.2.0 | 8 / 7 | |
| 0.1.1 | 8 / 6 | |
| 0.1.0 | 8 / 6 | |
| 0.0.0 | 0 / 1 |
v9.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.