jsdoc — Greenflagged

An API documentation generator for JavaScript.

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

hegemonic

Keywords

documentationjavascript

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Lack of Sigstore provenance is a best-practice gap, not a security defect; jsdoc's long history and ecosystem trust mitigate this.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): hegemonic is the known long-term jsdoc maintainer; removal of kzh is routine housekeeping, not a takeover signal.	ai	2026/04/24
semgrep	semgrep:eval-usage	AI (semgrep): eval() loads local Jake/lib/mustache.js for build-time template rendering in Jakefile.js; standard pattern for 2013-era build tools.	ai	2026/04/24
source-diff	net-exec-file:Jakefile.js	AI (source-diff): Jakefile.js is a build task using eval on a local Mustache file, not a dropper. No actual network calls present. False positive.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): hegemonic (Jeff Williams) is a long-standing core jsdoc maintainer with 104 approved packages and 4900+ day history.	ai	2026/04/24
npm-metadata	url-dep:taffydb	AI (npm-metadata): Points to hegemonic's own fork on GitHub; common practice for 2013-era npm packages. Maintainer-owned repo.	ai	2026/04/24
npm-metadata	url-dep:crypto-browserify	AI (npm-metadata): Points to dominictarr/crypto-browserify with pinned commit hash; well-known package, common 2013-era practice.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): @jsdoc/salty is a first-party replacement for taffydb under the same jsdoc GitHub org; the dependency swap is intentional and low-risk.	ai	2026/04/24
phantom-deps	phantom-dep:@types/markdown-it	AI (phantom-deps): Type definitions are correctly declared; loaded by convention for markdown-it support.	ai	2026/04/24
phantom-deps	phantom-dep:klaw	AI (phantom-deps): klaw is legitimately declared and used for filesystem traversal; false positive.	ai	2026/04/24
dependencies	unvetted-dep:markdown-it	AI (dependencies): markdown-it is a well-known, widely-used Markdown parser; its use in jsdoc for rendering documentation comments is expected and legitimate.	ai	2026/04/23
semgrep	semgrep:dynamic-require	AI (semgrep): jsdoc intentionally loads user-specified config files via dynamic require in its CLI. This is documented behavior, not a security risk — the path is user-controlled by design.	ai	2026/04/23

Versions (showing 30 of 30)

Version	Deps	Published
4.0.5	15 / 5	2025-10-08
4.0.4	15 / 5	2024-10-19
4.0.3	15 / 5	2024-05-02
4.0.2	15 / 5	2023-02-19
4.0.1	15 / 5	2023-02-16
4.0.0	15 / 5	2022-11-03
3.6.11	15 / 5	2022-07-20
3.6.10	15 / 5	2022-01-25
3.6.7	14 / 5	2021-05-15
3.6.6	14 / 5	2020-09-20
3.6.5	14 / 5	2020-07-22
3.6.4	14 / 5	2020-04-06
3.6.3	14 / 5	2019-07-14
3.6.2	14 / 5	2019-05-12
3.6.1	14 / 5	2019-05-05
3.6.0	14 / 5	2019-05-04
3.5.5	12 / 5	2017-09-14
3.5.4	12 / 5	2017-08-04
3.5.3	12 / 5	2017-07-14
3.5.2	12 / 5	2017-07-12
3.5.1	12 / 5	2017-07-10
3.5.0	12 / 5	2017-07-10
3.4.3	12 / 5	2016-11-10
3.4.2	12 / 5	2016-10-03
3.3.3	11 / 6	2015-09-22
3.3.2	11 / 6	2015-06-13
3.3.1	11 / 6	2015-06-07
3.3.0	11 / 6	2015-05-11
3.2.2	9 / 0	2013-11-04
0.0.0	0 / 0	2011-09-19

v4.0.5

1 finding

LOW No provenance attestation provenance

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

v4.0.4

1 finding

LOW No provenance attestation provenance

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

v4.0.3

1 finding

LOW No provenance attestation provenance

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

v4.0.2

1 finding

LOW No provenance attestation provenance

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

v4.0.1

1 finding

INFO No provenance attestation provenance

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

v4.0.0

1 finding

INFO No provenance attestation provenance

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

v3.6.11

1 finding

INFO No provenance attestation provenance

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

v3.6.10

1 finding

LOW No provenance attestation provenance

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

v3.6.7

1 finding

LOW No provenance attestation provenance

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

v3.6.6

1 finding

INFO No provenance attestation provenance

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

v3.6.5

1 finding

LOW No provenance attestation provenance

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

v3.6.4

1 finding

LOW No provenance attestation provenance

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

v3.6.3

1 finding

LOW No provenance attestation provenance

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

v3.6.2

1 finding

LOW No provenance attestation provenance

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

v3.6.1

1 finding

INFO No provenance attestation provenance

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

v3.6.0

1 finding

INFO No provenance attestation provenance

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

v3.5.5

1 finding

LOW No provenance attestation provenance

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

v3.5.4

1 finding

LOW No provenance attestation provenance

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

v3.5.3

1 finding

INFO No provenance attestation provenance

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

v3.5.2

1 finding

LOW No provenance attestation provenance

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

v3.5.1

1 finding

LOW No provenance attestation provenance

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

v3.5.0

1 finding

INFO No provenance attestation provenance

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

v3.4.3

1 finding

LOW No provenance attestation provenance

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

v3.4.2

1 finding

LOW No provenance attestation provenance

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

v3.3.3

1 finding

INFO No provenance attestation provenance

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

v3.3.2

1 finding

LOW No provenance attestation provenance

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

v3.3.1

1 finding

LOW No provenance attestation provenance

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

v3.3.0

1 finding

LOW No provenance attestation provenance

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

v3.2.2

2 findings

HIGH New file with network + code execution: Jakefile.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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