← Home

watch

npm Repository Homepage

Utilities for watching file trees.

30
Versions
Apache-2.0
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

finnpaulslevithomasonmikeal

Keywords

utilutilityfsfiles

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): watch's core feature is executing user-specified commands on file changes; child_process exec in cli.js is fundamental to the package's documented purpose. ai
maintainer-change maintainer-added AI (maintainer-change): Publisher transition to finnpauls occurred in 2014 (~11 years ago); finnpauls has a clean track record (34 approved, 0 rejected). Long-settled, legitimate handoff. ai
publish-pattern new-deps-added AI (publish-pattern): minimist is a well-established arg-parsing library added for the CLI binary; entirely consistent with the package's purpose and not suspicious. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require in cli.js is intentional: it loads a user-specified filter module passed via CLI flag. This is documented behavior, not a supply-chain risk. ai
provenance publisher-changed AI (provenance): Publisher change from finnpauls to mikeal occurred in 2016; mikeal is the original author per package.json and GitHub repo. Historical, legitimate transition. ai

Versions (showing 30 of 30)

Version Deps Published
1.0.2 2 / 0
1.0.1 2 / 0
1.0.0 2 / 0
0.19.3 2 / 0
0.19.2 2 / 0
0.19.1 2 / 0
0.18.0 2 / 0
0.17.1 2 / 0
0.17.0 3 / 0
0.16.0 2 / 0
0.15.0 2 / 0
0.14.0 2 / 0
0.13.0 1 / 0
0.12.0 0 / 0
0.11.0 0 / 0
0.10.0 0 / 0
0.9.0 0 / 0
0.8.0 0 / 0
0.7.0 0 / 0
0.6.0 0 / 0
0.5.1 0 / 0
0.5.0 0 / 0
0.4.0 0 / 0
0.3.3 0 / 0
0.3.2 0 / 0
0.3.1 0 / 0
0.3.0 0 / 0
0.2.1 0 / 0
0.2.0 0 / 0
0.1.0 0 / 0

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v0.19.2

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: mikeal → levithomason (on 2016-08-16) provenance

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

v0.19.1

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: mikeal → levithomason (on 2016-06-20) provenance

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

v0.18.0

2 findings
HIGH Publisher changed: finnpauls → mikeal (on 2016-04-29) provenance

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

v0.17.1

1 finding
LOW No provenance attestation provenance

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

v0.17.0

1 finding
LOW No provenance attestation provenance

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

v0.16.0

1 finding
LOW No provenance attestation provenance

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

v0.15.0

1 finding
LOW No provenance attestation provenance

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

v0.14.0

1 finding
LOW No provenance attestation provenance

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

v0.13.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: mikeal → finnpauls (on 2014-10-27) provenance

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

v0.12.0

1 finding
LOW No provenance attestation provenance

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

v0.11.0

1 finding
LOW No provenance attestation provenance

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

v0.10.0

1 finding
LOW No provenance attestation provenance

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

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.8.0

1 finding
LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.1

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.3

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.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.2.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.

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

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