@zuzjs/hooks MIT 32 versions

@zuzjs/hooks

npm Repository Homepage

ZuzJS Hooks

32

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

zuzpk

Keywords

reactzuzzuz.jszuz uizuzui

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:md5	AI (phantom-deps): Utility library; dependencies likely re-exported or used in examples.	ai	2026/05/27
phantom-deps	phantom-dep:moment	AI (phantom-deps): Utility library; dependencies likely re-exported or used in examples.	ai	2026/05/27
phantom-deps	phantom-dep:nanoid	AI (phantom-deps): Utility library; dependencies likely re-exported or used in examples.	ai	2026/05/27
phantom-deps	phantom-dep:hashids	AI (phantom-deps): Utility library; dependencies likely re-exported or used in examples.	ai	2026/05/27
phantom-deps	phantom-dep:chokidar	AI (phantom-deps): Utility library; dependencies likely re-exported or used in examples.	ai	2026/05/27
phantom-deps	phantom-dep:date-fns	AI (phantom-deps): Utility library; dependencies likely re-exported or used in examples.	ai	2026/05/27
phantom-deps	phantom-dep:commander	AI (phantom-deps): Utility library; dependencies likely re-exported or used in examples.	ai	2026/05/27
phantom-deps	phantom-dep:js-cookie	AI (phantom-deps): Utility library; dependencies likely re-exported or used in examples.	ai	2026/05/27
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): Utility library; dependencies likely re-exported or used in examples.	ai	2026/05/27
phantom-deps	phantom-dep:@types/md5	AI (phantom-deps): Type definitions for re-exported utilities.	ai	2026/05/27
phantom-deps	phantom-dep:picocolors	AI (phantom-deps): Utility library; dependencies likely re-exported or used in examples.	ai	2026/05/27
phantom-deps	phantom-dep:@types/react	AI (phantom-deps): Type definitions for React peer dependency.	ai	2026/05/27
phantom-deps	phantom-dep:@types/react-dom	AI (phantom-deps): Type definitions for React peer dependency.	ai	2026/05/27

Versions (showing 32 of 32)

Version	Deps	Published
0.1.33	16 / 0	2026-05-31
0.1.32	16 / 0	2026-05-31
0.1.31	16 / 0	2026-05-31
0.1.30	16 / 0	2026-05-19
0.1.29	16 / 0	2026-05-17
0.1.28	16 / 0	2026-05-14
0.1.27	16 / 0	2026-05-02
0.1.26	16 / 0	2026-05-01
0.1.25	16 / 0	2026-04-30
0.1.24	16 / 0	2026-04-28
0.1.23	16 / 0	2026-04-26
0.1.22	16 / 0	2026-04-24
0.1.21	16 / 0	2026-04-23
0.1.20	16 / 0	2026-04-11
0.1.19	16 / 0	2026-04-01
0.1.18	16 / 0	2026-04-01
0.1.17	16 / 0	2026-03-13
0.1.16	16 / 0	2026-03-06
0.1.15	16 / 0	2026-03-04
0.1.14	16 / 0	2026-03-03
0.1.13	16 / 0	2026-03-02
0.1.12	16 / 0	2026-02-28
0.1.11	16 / 0	2026-02-24
0.1.10	16 / 0	2026-02-23
0.1.9	15 / 0	2026-02-23
0.1.8	15 / 0	2026-02-22
0.1.7	15 / 0	2026-02-18
0.1.6	15 / 0	2026-02-17
0.1.5	15 / 0	2026-02-13
0.1.4	15 / 0	2026-02-12
0.1.3	15 / 0	2026-02-11
0.1.2	15 / 0	2026-02-08

v0.1.33

1 finding

LOW No provenance attestation provenance

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

v0.1.32

1 finding

LOW No provenance attestation provenance

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

v0.1.31

1 finding

LOW No provenance attestation provenance

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

v0.1.30

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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