jest-docblock MIT 50 versions

jest-docblock

npm Repository

50

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

aaronabramovsimenbrickhanloniiopenjs-operationscpojer

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	suspicious-initial-version	AI (npm-metadata): 0.0.0 is a known placeholder in Jest monorepo; package has 125 versions and 47M weekly downloads.	ai	2026/05/22
dependencies	unvetted-dep:detect-newline	AI (dependencies): detect-newline is a well-known sindresorhus utility; stable and benign dependency for this package.	ai	2026/04/23
npm-metadata	no-description	AI (npm-metadata): jest-docblock is a Jest monorepo sub-package; missing description is a known pattern for these packages and not a malice indicator.	ai	2026/04/23
provenance	publisher-changed	AI (provenance): Publisher change from cpojer to mjesun reflects a documented Jest team transition at Facebook; both are known contributors with strong track records.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): Inflated semver and missing metadata are expected for Jest monorepo sub-packages that follow Jest's versioning scheme. Not indicative of spam or malice.	ai	2026/04/21

Versions (showing 50 of 50)

Version	Deps	Published
30.4.0	1 / 1	2026-05-07
30.2.0	1 / 1	2025-09-28
30.0.1	1 / 1	2025-06-18
30.0.0	1 / 1	2025-06-10
29.7.0	1 / 1	2023-09-12
29.6.3	1 / 1	2023-08-21
29.4.3	1 / 1	2023-02-15
29.4.2	1 / 1	2023-02-07
29.2.0	1 / 1	2022-10-14
29.0.0	1 / 1	2022-08-25
28.1.1	1 / 1	2022-06-07
28.0.2	1 / 1	2022-04-27
28.0.0	1 / 1	2022-04-25
27.5.1	1 / 1	2022-02-08
27.5.0	1 / 1	2022-02-05
27.4.0	1 / 1	2021-11-29
27.0.6	1 / 1	2021-06-28
27.0.1	1 / 1	2021-05-25
26.0.0	1 / 1	2020-05-04
25.3.0	1 / 1	2020-04-08
25.2.6	1 / 1	2020-04-02
25.2.3	1 / 1	2020-03-26
25.2.0	1 / 1	2020-03-25
25.1.0	1 / 0	2020-01-22
25.0.0	1 / 0	2019-08-22
24.9.0	1 / 1	2019-08-16
24.3.0	1 / 1	2019-03-07
24.2.0	1 / 1	2019-03-05
24.0.0	1 / 0	2019-01-25
23.2.0	1 / 0	2018-06-25
23.0.1	1 / 0	2018-05-27
22.4.3	1 / 0	2018-03-21
22.4.0	1 / 0	2018-02-20
22.2.2	1 / 0	2018-02-09
22.2.0	1 / 0	2018-02-07
22.1.0	1 / 0	2018-01-15
22.0.6	1 / 0	2018-01-11
22.0.3	1 / 0	2017-12-19
22.0.2	1 / 0	2017-12-19
22.0.1	1 / 0	2017-12-18
22.0.0	1 / 0	2017-12-18
21.2.0	0 / 0	2017-09-26
21.1.0	0 / 0	2017-09-14
21.0.2	0 / 0	2017-09-08
21.0.0	0 / 0	2017-09-04
20.0.3	0 / 0	2017-05-17
20.0.2	0 / 0	2017-05-17
20.0.1	0 / 0	2017-05-11
20.0.0	0 / 0	2017-05-06
0.0.0	0 / 0	2017-03-03

v30.4.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: cpojer → simenb (on 2026-05-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-07. This could indicate a legitimate maintainer transition or an account compromise.

v30.0.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.

v30.0.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.

v29.7.0

1 finding

LOW No provenance attestation provenance

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

v29.6.3

1 finding

LOW No provenance attestation provenance

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

v29.4.3

1 finding

LOW No provenance attestation provenance

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

v29.4.2

1 finding

LOW No provenance attestation provenance

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

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

v29.0.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.

v28.1.1

2 findings

HIGH Publisher changed: cpojer → simenb (on 2022-06-07) provenance

This version was published by a different npm account than previous versions on 2022-06-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v28.0.2

2 findings

HIGH Publisher changed: cpojer → simenb (on 2022-04-27) provenance

This version was published by a different npm account than previous versions on 2022-04-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v28.0.0

2 findings

HIGH Publisher changed: cpojer → simenb (on 2022-04-25) provenance

This version was published by a different npm account than previous versions on 2022-04-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.5.1

2 findings

HIGH Publisher changed: cpojer → simenb (on 2022-02-08) provenance

This version was published by a different npm account than previous versions on 2022-02-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.5.0

2 findings

HIGH Publisher changed: cpojer → simenb (on 2022-02-05) provenance

This version was published by a different npm account than previous versions on 2022-02-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.4.0

2 findings

HIGH Publisher changed: cpojer → simenb (on 2021-11-29) provenance

This version was published by a different npm account than previous versions on 2021-11-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.0.6

2 findings

HIGH Publisher changed: cpojer → simenb (on 2021-06-28) provenance

This version was published by a different npm account than previous versions on 2021-06-28. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.0.1

2 findings

HIGH Publisher changed: cpojer → simenb (on 2021-05-25) provenance

This version was published by a different npm account than previous versions on 2021-05-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v26.0.0

2 findings

HIGH Publisher changed: cpojer → simenb (on 2020-05-04) provenance

This version was published by a different npm account than previous versions on 2020-05-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.3.0

2 findings

HIGH Publisher changed: cpojer → simenb (on 2020-04-08) provenance

This version was published by a different npm account than previous versions on 2020-04-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.2.6

2 findings

HIGH Publisher changed: cpojer → simenb (on 2020-04-02) provenance

This version was published by a different npm account than previous versions on 2020-04-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.2.3

2 findings

HIGH Publisher changed: cpojer → simenb (on 2020-03-26) provenance

This version was published by a different npm account than previous versions on 2020-03-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.2.0

2 findings

HIGH Publisher changed: cpojer → simenb (on 2020-03-25) provenance

This version was published by a different npm account than previous versions on 2020-03-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.1.0

2 findings

HIGH Publisher changed: cpojer → davidzilburg (on 2020-01-22) provenance

This version was published by a different npm account than previous versions on 2020-01-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.0.0

2 findings

HIGH Publisher changed: cpojer → scotthovestadt (on 2019-08-22) provenance

This version was published by a different npm account than previous versions on 2019-08-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v24.9.0

2 findings

HIGH Publisher changed: cpojer → scotthovestadt (on 2019-08-16) provenance

This version was published by a different npm account than previous versions on 2019-08-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v24.3.0

2 findings

HIGH Publisher changed: cpojer → rubennorte (on 2019-03-07) provenance

This version was published by a different npm account than previous versions on 2019-03-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v24.2.0

2 findings

HIGH Publisher changed: cpojer → mjesun (on 2019-03-05) provenance

This version was published by a different npm account than previous versions on 2019-03-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v24.0.0

2 findings

HIGH Publisher changed: cpojer → rubennorte (on 2019-01-25) provenance

This version was published by a different npm account than previous versions on 2019-01-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v23.2.0

2 findings

HIGH Publisher changed: cpojer → mjesun (on 2018-06-25) provenance

This version was published by a different npm account than previous versions on 2018-06-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v23.0.1

2 findings

HIGH Publisher changed: cpojer → mjesun (on 2018-05-27) provenance

This version was published by a different npm account than previous versions on 2018-05-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v22.4.3

2 findings

HIGH Publisher changed: cpojer → mjesun (on 2018-03-21) provenance

This version was published by a different npm account than previous versions on 2018-03-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v22.4.0

2 findings

HIGH Publisher changed: cpojer → mjesun (on 2018-02-20) provenance

This version was published by a different npm account than previous versions on 2018-02-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v22.2.2

2 findings

HIGH Publisher changed: cpojer → mjesun (on 2018-02-09) provenance

This version was published by a different npm account than previous versions on 2018-02-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v22.2.0

2 findings

HIGH Publisher changed: cpojer → mjesun (on 2018-02-07) provenance

This version was published by a different npm account than previous versions on 2018-02-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v22.1.0

1 finding

LOW No provenance attestation provenance

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

v22.0.6

1 finding

LOW No provenance attestation provenance

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

v22.0.3

1 finding

LOW No provenance attestation provenance

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

v22.0.2

1 finding

LOW No provenance attestation provenance

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

v22.0.1

1 finding

LOW No provenance attestation provenance

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

v22.0.0

2 findings

HIGH Publisher changed: cpojer → mjesun (on 2017-12-18) provenance

This version was published by a different npm account than previous versions on 2017-12-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v21.2.0

1 finding

LOW No provenance attestation provenance

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

v21.1.0

1 finding

LOW No provenance attestation provenance

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

v21.0.2

1 finding

LOW No provenance attestation provenance

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

v21.0.0

1 finding

LOW No provenance attestation provenance

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

v20.0.3

1 finding

LOW No provenance attestation provenance

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

v20.0.2

1 finding

LOW No provenance attestation provenance

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

v20.0.1

1 finding

LOW No provenance attestation provenance

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

v20.0.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.

v0.0.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.