gaze MIT 30 versions

gaze

npm Repository Homepage

A globbing fs.watch wrapper built from the best parts of other fine watch libs.

30

Versions

MIT

License

Yes

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

alexgorbatchevjoshperryshama

Keywords

watchglob

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:globule	AI (dependencies): globule is a legitimate, well-known glob utility and a stable dependency of gaze across many versions.	ai	2026/04/23
install-scripts	install-script:install	AI (install-scripts): gaze uses native bindings (nan/bindings/node-gyp); node-gyp rebuild is the standard and expected install script for this package.	ai	2026/04/23
phantom-deps	phantom-dep:nan	AI (phantom-deps): nan is referenced in binding.gyp for native compilation, not imported in JS — this is the standard usage pattern for nan.	ai	2026/04/23
provenance	no-provenance	AI (provenance): Lack of Sigstore provenance is common (~88% of npm packages) and not a risk signal for this well-established package.	ai	2026/04/21

Versions (showing 30 of 30)

Version	Deps	Published
1.1.3	1 / 8	2018-05-21
1.1.2	1 / 8	2016-09-27
1.1.1	1 / 8	2016-08-05
1.1.0	1 / 8	2016-06-25
1.0.0	1 / 8	2016-03-12
0.6.3	5 / 7	2014-04-15
0.6.1	5 / 7	2014-04-14
0.6.0	4 / 7	2014-04-13
0.5.2	1 / 7	2015-10-05
0.5.1	1 / 7	2014-02-23
0.5.0	1 / 5	2014-02-06
0.4.3	1 / 4	2013-10-19
0.4.2	1 / 4	2013-09-25
0.4.1	1 / 4	2013-07-09
0.4.0	1 / 4	2013-07-01
0.3.4	2 / 4	2013-05-03
0.3.3	2 / 4	2013-02-14
0.3.2	4 / 5	2013-01-07
0.3.1	4 / 4	2012-12-17
0.3.0	4 / 4	2012-12-14
0.2.2	4 / 4	2012-12-04
0.2.1	4 / 2	2012-11-01
0.2.0	4 / 2	2012-10-23
0.1.6	4 / 2	2012-10-16
0.1.5	4 / 2	2012-10-09
0.1.4	4 / 2	2012-10-08
0.1.3	4 / 2	2012-10-08
0.1.2	4 / 2	2012-10-08
0.1.1	4 / 2	2012-10-05
0.1.0	4 / 2	2012-10-04

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

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

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

v1.0.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.3

2 findings

HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild

INFO No provenance attestation provenance

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

v0.6.1

2 findings

HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild

INFO No provenance attestation provenance

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

v0.6.0

2 findings

HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild

INFO No provenance attestation provenance

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

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

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

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

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

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

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

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

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

v0.3.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

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

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

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

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

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

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

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

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

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

v0.1.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] 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

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.