@types/chokidar MIT 16 versions

@types/chokidar

npm

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

16

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/reppners/	AI (email-domain): The 'email' field contains a GitHub profile URL, not an email address. The analyzer misidentifies github.com as an unclaimed domain. This is a stable false positive for this DefinitelyTyped package.	ai	2026/04/24
phantom-deps	phantom-dep:@types/node	AI (phantom-deps): @types/node is a type-only dependency in a TypeScript definitions package; it does not need to be directly imported. This is expected behavior for @types packages.	ai	2026/04/24

Versions (showing 16 of 16)

Version	Deps	Published
2.1.7	1 / 0	2024-10-23
2.1.6	1 / 0	2024-10-23
2.1.5	1 / 0	2024-10-23
2.1.4	1 / 0	2024-10-23
2.1.3	1 / 0	2019-03-06
1.7.5	2 / 0	2018-02-26
1.7.4	2 / 0	2017-12-05
1.7.3	1 / 0	2017-09-20
1.7.2	1 / 0	2017-08-21
1.7.1	1 / 0	2017-07-25
1.7.0	1 / 0	2017-06-06
1.6.0	1 / 0	2017-03-23
1.4.31	1 / 0	2017-01-02
1.4.30	1 / 0	2016-12-12
1.4.29	1 / 0	2016-09-19
1.4.28	1 / 0	2016-07-14

v2.1.7

1 finding

LOW No provenance attestation provenance

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

v2.1.6

1 finding

LOW No provenance attestation provenance

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

v2.1.5

1 finding

LOW No provenance attestation provenance

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

v2.1.4

1 finding

LOW No provenance attestation provenance

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

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v1.7.5

1 finding

LOW No provenance attestation provenance

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

v1.7.4

1 finding

LOW No provenance attestation provenance

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

v1.7.3

1 finding

LOW No provenance attestation provenance

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

v1.7.2

1 finding

LOW No provenance attestation provenance

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

v1.7.1

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.4.31

1 finding

LOW No provenance attestation provenance

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

v1.4.30

1 finding

LOW No provenance attestation provenance

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

v1.4.29

1 finding

LOW No provenance attestation provenance

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

v1.4.28

2 findings

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

Maintainer email 'https://github.com/reppners/' uses domain 'https://github.com/reppners/' 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.