gulp-watch
Watch, that actually is an endless stream
Supply chain provenance
Status for the latest visible version.
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
Keywords
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 | |
| provenance | no-provenance | AI (provenance): Published in 2018, before Sigstore provenance existed. Expected for this era of packages. | ai |
Versions (showing 81 of 81)
| Version | Deps | Published |
|---|---|---|
| 5.0.1 | 12 / 11 | |
| 5.0.0 | 10 / 11 | |
| 4.3.11 | 10 / 11 | |
| 4.3.10 | 9 / 11 | |
| 4.3.9 | 9 / 11 | |
| 4.3.8 | 9 / 11 | |
| 4.3.7 | 9 / 11 | |
| 4.3.6 | 9 / 11 | |
| 4.3.5 | 9 / 10 | |
| 4.3.4 | 9 / 10 | |
| 4.3.3 | 9 / 10 | |
| 4.3.2 | 9 / 10 | |
| 4.3.1 | 9 / 11 | |
| 4.3.0 | 9 / 11 | |
| 4.2.5 | 9 / 11 | |
| 4.2.4 | 9 / 11 | |
| 4.2.3 | 9 / 11 | |
| 4.2.2 | 9 / 11 | |
| 4.2.1 | 8 / 11 | |
| 4.2.0 | 8 / 11 | |
| 4.1.1 | 8 / 11 | |
| 4.1.0 | 7 / 11 | |
| 4.0.3 | 7 / 11 | |
| 4.0.2 | 7 / 11 | |
| 4.0.1 | 8 / 11 | |
| 4.0.0 | 8 / 11 | |
| 3.0.0 | 7 / 11 | |
| 2.0.0 | 8 / 11 | |
| 1.2.1 | 8 / 11 | |
| 1.2.0 | 8 / 11 | |
| 1.1.1 | 8 / 11 | |
| 1.1.0 | 8 / 11 | |
| 1.0.8 | 8 / 11 | |
| 1.0.7 | 8 / 11 | |
| 1.0.6 | 8 / 11 | |
| 1.0.5 | 8 / 11 | |
| 1.0.4 | 8 / 11 | |
| 1.0.3 | 8 / 11 | |
| 1.0.2 | 9 / 11 | |
| 1.0.0 | 9 / 12 | |
| 0.7.1 | 8 / 12 | |
| 0.7.0 | 8 / 12 | |
| 0.6.10 | 8 / 12 | |
| 0.6.9 | 8 / 18 | |
| 0.6.8 | 8 / 18 | |
| 0.6.7 | 7 / 18 | |
| 0.6.6 | 6 / 18 | |
| 0.6.5 | 6 / 18 | |
| 0.6.4 | 6 / 15 | |
| 0.6.3 | 6 / 15 | |
| 0.6.2 | 6 / 16 | |
| 0.6.1 | 6 / 16 | |
| 0.6.0 | 6 / 16 | |
| 0.5.4 | 6 / 17 | |
| 0.5.3 | 6 / 17 | |
| 0.5.2 | 6 / 17 | |
| 0.5.0 | 6 / 17 | |
| 0.4.2 | 5 / 9 | |
| 0.4.1 | 5 / 9 | |
| 0.4.0 | 5 / 9 | |
| 0.3.4 | 5 / 9 | |
| 0.3.3 | 5 / 7 | |
| 0.3.2 | 5 / 7 | |
| 0.3.1 | 6 / 3 | |
| 0.3.0 | 6 / 3 | |
| 0.2.7 | 6 / 1 | |
| 0.2.6 | 6 / 1 | |
| 0.2.5 | 6 / 1 | |
| 0.2.4 | 6 / 1 | |
| 0.2.3 | 5 / 1 | |
| 0.2.2 | 5 / 1 | |
| 0.2.1 | 5 / 1 | |
| 0.2.0 | 5 / 2 | |
| 0.1.3 | 5 / 2 | |
| 0.1.2 | 4 / 2 | |
| 0.1.1 | 4 / 2 | |
| 0.1.0 | 4 / 2 | |
| 0.0.4 | 3 / 3 | |
| 0.0.3 | 2 / 3 | |
| 0.0.2 | 3 / 3 | |
| 0.0.1 | 1 / 5 |
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.