gulp-watch MIT 51 versions

gulp-watch

npm Repository Homepage

Watch, that actually is an endless stream

51

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

floatdropult_combo

Keywords

gulpwatchgulpplugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): floatdrop is the original author and repo owner; ult_combo was a co-maintainer. This is not a suspicious takeover.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Published in 2018, before Sigstore provenance existed. Expected for this era of packages.	ai	2026/04/24

Versions (showing 51 of 81)

View all versions

Version	Deps	Published
5.0.1	12 / 11	2018-07-23
5.0.0	10 / 11	2018-01-07
4.3.11	10 / 11	2016-11-19
4.3.10	9 / 11	2016-09-27
4.3.9	9 / 11	2016-07-25
4.3.8	9 / 11	2016-06-19
4.3.7	9 / 11	2016-06-19
4.3.6	9 / 11	2016-05-23
4.3.5	9 / 10	2015-08-19
4.3.4	9 / 10	2015-07-26
4.3.3	9 / 10	2015-07-16
4.3.2	9 / 10	2015-07-15
4.3.1	9 / 11	2015-07-13
4.3.0	9 / 11	2015-07-13
4.2.5	9 / 11	2015-07-13
4.2.4	9 / 11	2015-04-08
4.2.3	9 / 11	2015-04-04
4.2.2	9 / 11	2015-03-30
4.2.1	8 / 11	2015-03-27
4.2.0	8 / 11	2015-03-16
4.1.1	8 / 11	2015-02-08
4.1.0	7 / 11	2015-01-23
4.0.3	7 / 11	2015-01-23
4.0.2	7 / 11	2015-01-22
4.0.1	8 / 11	2015-01-21
4.0.0	8 / 11	2015-01-21
3.0.0	7 / 11	2014-12-02
2.0.0	8 / 11	2014-11-20
1.2.1	8 / 11	2014-11-20
1.2.0	8 / 11	2014-11-14
1.1.1	8 / 11	2014-11-20
1.1.0	8 / 11	2014-10-09
1.0.8	8 / 11	2014-11-20
1.0.7	8 / 11	2014-09-20
1.0.6	8 / 11	2014-09-20
1.0.5	8 / 11	2014-09-16
1.0.4	8 / 11	2014-09-14
1.0.3	8 / 11	2014-09-11
1.0.2	9 / 11	2014-09-06
1.0.0	9 / 12	2014-09-05
0.7.1	8 / 12	2014-09-05
0.7.0	8 / 12	2014-08-29
0.6.10	8 / 12	2014-08-28
0.6.9	8 / 18	2014-07-28
0.6.8	8 / 18	2014-06-21
0.6.7	7 / 18	2014-06-20
0.6.6	6 / 18	2014-06-12
0.6.5	6 / 18	2014-05-22
0.6.4	6 / 15	2014-04-30
0.6.3	6 / 15	2014-04-29
0.6.2	6 / 16	2014-04-17

v5.0.1

1 finding

LOW No provenance attestation provenance

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

v5.0.0

2 findings

HIGH Publisher changed: ult_combo → floatdrop (on 2018-01-07) provenance

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

v4.3.11

1 finding

INFO No provenance attestation provenance

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

v4.3.10

1 finding

INFO No provenance attestation provenance

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

v4.3.9

1 finding

INFO No provenance attestation provenance

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

v4.3.8

1 finding

INFO No provenance attestation provenance

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

v4.3.7

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: floatdrop → ult_combo (on 2016-06-19) provenance

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

v4.3.6

1 finding

INFO No provenance attestation provenance

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

v4.3.5

1 finding

INFO No provenance attestation provenance

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

v4.3.4

1 finding

INFO No provenance attestation provenance

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

v4.3.3

1 finding

INFO No provenance attestation provenance

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

v4.3.2

1 finding

INFO No provenance attestation provenance

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

v4.3.1

1 finding

INFO No provenance attestation provenance

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

v4.3.0

1 finding

INFO No provenance attestation provenance

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

v4.2.5

1 finding

INFO No provenance attestation provenance

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

v4.2.4

1 finding

INFO No provenance attestation provenance

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

v4.2.3

1 finding

INFO No provenance attestation provenance

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

v4.2.2

1 finding

INFO No provenance attestation provenance

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

v4.2.1

1 finding

INFO No provenance attestation provenance

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

v4.2.0

1 finding

INFO No provenance attestation provenance

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

v4.1.1

1 finding

INFO No provenance attestation provenance

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

v4.1.0

1 finding

INFO No provenance attestation provenance

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

v4.0.3

1 finding

INFO No provenance attestation provenance

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

v4.0.2

1 finding

INFO No provenance attestation provenance

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

v4.0.1

1 finding

INFO No provenance attestation provenance

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

v4.0.0

1 finding

INFO No provenance attestation provenance

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