watchpack MIT 30 versions

watchpack

npm Repository Homepage

Wrapper library for directory and file watching.

30

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

sokraevilebottnawi

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:chokidar2	AI (dependencies): chokidar2 is a local file dependency bundled within the package tarball itself (files includes chokidar2 dir). Content is fixed at publish time, not an external URL that can be swapped.	ai	2026/04/24
npm-metadata	url-dep:chokidar2	AI (npm-metadata): file:./chokidar2 points to a bundled directory included in the package tarball, not an external mutable URL. This is a deliberate design for chokidar v2/v3 compatibility.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): The new chokidar2 dep is a bundled local directory (file:./chokidar2) included in the tarball. Not an external registry dep that could be hijacked.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): evilebottnawi is a known webpack core contributor; publisher change from sokra reflects legitimate webpack org maintainer transition, stable for this package.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): evilebottnawi is a long-standing webpack ecosystem contributor; addition reflects legitimate org-level maintainer transition for this webpack package.	ai	2026/04/24

Versions (showing 30 of 30)

Version	Deps	Published
2.5.1	2 / 22	2026-01-15
2.5.0	2 / 22	2025-12-23
2.4.4	2 / 10	2025-05-21
2.4.3	2 / 10	2025-05-19
2.4.2	2 / 10	2024-08-13
2.4.1	2 / 10	2024-03-13
2.4.0	2 / 10	2022-06-02
2.3.1	2 / 10	2021-12-06
2.3.0	2 / 10	2021-11-24
2.2.0	2 / 10	2021-05-19
2.1.1	2 / 10	2021-02-07
2.1.0	2 / 10	2020-12-08
2.0.1	2 / 10	2020-10-31
2.0.0	2 / 10	2020-09-17
1.7.5	4 / 7	2020-11-10
1.7.4	4 / 7	2020-07-24
1.7.3	4 / 7	2020-07-24
1.7.2	4 / 7	2020-05-16
1.7.1	4 / 7	2020-05-16
1.6.1	3 / 7	2020-03-26
1.6.0	3 / 7	2018-04-26
1.5.0	3 / 7	2018-02-28
1.4.0	3 / 7	2017-07-15
1.3.1	3 / 7	2017-02-22
1.3.0	3 / 7	2017-02-22
1.2.1	3 / 7	2017-02-13
1.2.0	3 / 7	2016-12-30
1.1.0	3 / 6	2016-05-06
1.0.1	3 / 6	2016-02-09
1.0.0	3 / 6	2016-02-09

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.4

1 finding

LOW No provenance attestation provenance

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

v2.4.3

1 finding

LOW No provenance attestation provenance

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

v2.4.2

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.

v2.4.1

2 findings

HIGH Publisher changed: sokra → evilebottnawi (on 2024-03-13) provenance

This version was published by a different npm account than previous versions on 2024-03-13. 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.

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.1

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.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.

v2.1.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.

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

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

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

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

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

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

v1.1.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.

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

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