@types/cheerio MIT 40 versions

@types/cheerio

npm

Stub TypeScript definitions entry for cheerio, which provides its own types definitions

40

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
email-domain	unclaimed-email:https://github.com/blittle	AI (email-domain): False positive: 'https://github.com/blittle' is a GitHub URL in the author field, not an email domain. Standard DefinitelyTyped contributor format.	ai	2026/04/24
publish-pattern	dormant-publish	AI (publish-pattern): Stub migration packages in @types/* are published once when upstream bundles types; long dormancy before a single stub release is the expected lifecycle, not a takeover signal.	ai	2026/04/23
publish-pattern	new-deps-added	AI (publish-pattern): Adding cheerio as a dependency is the entire purpose of this stub package — it redirects @types/cheerio consumers to cheerio's own bundled types. This is the standard DefinitelyTyped migration pattern.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): Stub redirect packages in @types/* are intentionally minimal: no code, no README, no keywords. The deprecated field and single redirect dep are the complete, correct payload for this package type.	ai	2026/04/23
source-diff	source-size-dropped	AI (source-diff): Source dropping to 0B is expected — the stub intentionally ships no type definitions, delegating entirely to the cheerio package's own bundled types.	ai	2026/04/23
phantom-deps	phantom-dep:cheerio	AI (phantom-deps): Stub packages don't import anything; the cheerio dep exists solely to trigger npm installation of the real types. Phantom-dep finding is a stable false positive for this package.	ai	2026/04/23

Versions (showing 40 of 40)

Version	Deps	Published
1.0.0	1 / 0	2025-05-05
0.22.35	1 / 0	2023-11-20
0.22.34	1 / 0	2023-11-07
0.22.33	1 / 0	2023-10-17
0.22.32	1 / 0	2023-09-04
0.22.31	1 / 0	2022-02-05
0.22.30	1 / 0	2021-07-06
0.22.29	1 / 0	2021-05-21
0.22.28	1 / 0	2021-03-20
0.22.27	1 / 0	2021-03-12
0.22.26	1 / 0	2021-03-10
0.22.25	1 / 0	2021-03-08
0.22.24	1 / 0	2021-02-11
0.22.23	1 / 0	2020-12-08
0.22.22	1 / 0	2020-09-23
0.22.21	1 / 0	2020-07-08
0.22.20	1 / 0	2020-07-07
0.22.19	1 / 0	2020-07-06
0.22.18	1 / 0	2020-04-23
0.22.17	1 / 0	2020-03-20
0.22.16	1 / 0	2020-01-29
0.22.15	1 / 0	2019-12-03
0.22.14	1 / 0	2019-11-12
0.22.13	1 / 0	2019-08-09
0.22.12	1 / 0	2019-07-03
0.22.11	1 / 0	2019-03-06
0.22.10	0 / 0	2018-11-26
0.22.9	0 / 0	2018-08-23
0.22.8	0 / 0	2018-06-26
0.22.7	0 / 0	2017-12-30
0.22.6	0 / 0	2017-11-27
0.22.5	0 / 0	2017-10-31
0.22.4	0 / 0	2017-10-28
0.22.3	0 / 0	2017-10-09
0.22.2	0 / 0	2017-07-05
0.22.1	0 / 0	2017-03-27
0.22.0	0 / 0	2017-03-11
0.17.31	0 / 0	2016-10-05
0.17.30	0 / 0	2016-09-19
0.17.29	0 / 0	2016-07-14

v1.0.0

1 finding

LOW No provenance attestation provenance

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

v0.22.35

1 finding

LOW No provenance attestation provenance

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

v0.22.34

1 finding

LOW No provenance attestation provenance

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

v0.22.33

1 finding

LOW No provenance attestation provenance

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

v0.22.32

1 finding

LOW No provenance attestation provenance

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

v0.22.31

1 finding

LOW No provenance attestation provenance

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

v0.22.30

1 finding

LOW No provenance attestation provenance

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

v0.22.29

1 finding

LOW No provenance attestation provenance

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

v0.22.28

1 finding

LOW No provenance attestation provenance

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

v0.22.27

1 finding

LOW No provenance attestation provenance

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

v0.22.26

1 finding

LOW No provenance attestation provenance

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

v0.22.25

1 finding

LOW No provenance attestation provenance

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

v0.22.24

1 finding

LOW No provenance attestation provenance

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

v0.22.23

1 finding

LOW No provenance attestation provenance

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

v0.22.22

1 finding

LOW No provenance attestation provenance

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

v0.22.21

1 finding

LOW No provenance attestation provenance

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

v0.22.20

1 finding

LOW No provenance attestation provenance

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

v0.22.19

1 finding

LOW No provenance attestation provenance

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

v0.22.18

1 finding

LOW No provenance attestation provenance

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

v0.22.17

1 finding

LOW No provenance attestation provenance

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

v0.22.16

1 finding

LOW No provenance attestation provenance

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

v0.22.15

1 finding

LOW No provenance attestation provenance

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

v0.22.14

1 finding

LOW No provenance attestation provenance

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

v0.22.13

1 finding

LOW No provenance attestation provenance

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

v0.22.12

1 finding

LOW No provenance attestation provenance

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

v0.22.11

1 finding

LOW No provenance attestation provenance

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

v0.22.10

1 finding

LOW No provenance attestation provenance

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

v0.22.9

1 finding

LOW No provenance attestation provenance

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

v0.22.8

1 finding

LOW No provenance attestation provenance

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

v0.22.7

1 finding

LOW No provenance attestation provenance

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

v0.22.6

1 finding

LOW No provenance attestation provenance

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

v0.22.5

1 finding

LOW No provenance attestation provenance

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

v0.22.4

1 finding

LOW No provenance attestation provenance

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

v0.22.3

1 finding

LOW No provenance attestation provenance

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

v0.22.2

1 finding

LOW No provenance attestation provenance

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

v0.22.1

1 finding

LOW No provenance attestation provenance

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

v0.22.0

1 finding

LOW No provenance attestation provenance

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

v0.17.31

1 finding

LOW No provenance attestation provenance

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

v0.17.30

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.17.29

2 findings

HIGH Unclaimed maintainer email domain: https://github.com/blittle email-domain

Maintainer email 'https://github.com/blittle' uses domain 'https://github.com/blittle' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.