@wzyjs/next No license 56 versions

@wzyjs/next

npm

description

56

Versions

—

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

wzy1993

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:nuxt	AI (typosquat): Scoped package @wzyjs/next; not impersonating nuxt, different namespace and purpose.	ai	2026/05/14
typosquat	typosquat.levenshtein:jest	AI (typosquat): Scoped package @wzyjs/next; not impersonating jest, different namespace and purpose.	ai	2026/05/14
typosquat	typosquat.levenshtein:knex	AI (typosquat): Scoped package @wzyjs/next; not impersonating knex, different namespace and purpose.	ai	2026/05/14
phantom-deps	phantom-dep:@zenstackhq/sdk	AI (phantom-deps): @zenstackhq/sdk is declared as a dependency; used in config files as a ZenStack plugin dependency.	ai	2026/05/14

Versions (showing 56 of 56)

Version	Deps	Published
0.3.32	1 / 2	2026-05-11
0.3.31	1 / 2	2026-05-11
0.3.30	1 / 2	2026-05-11
0.3.29	1 / 2	2026-05-03
0.3.28	1 / 0	2026-04-30
0.3.27	1 / 0	2026-04-28
0.3.26	1 / 0	2026-04-24
0.3.25	1 / 0	2026-04-23
0.3.24	1 / 0	2026-04-22
0.3.23	1 / 0	2026-04-22
0.3.22	1 / 0	2026-04-22
0.3.20	1 / 0	2026-04-22
0.3.18	1 / 0	2026-04-14
0.3.17	1 / 0	2026-04-12
0.3.16	1 / 0	2026-04-12
0.3.10	1 / 0	2026-03-10
0.3.9	1 / 0	2026-03-03
0.3.8	1 / 0	2026-03-03
0.3.7	1 / 0	2026-03-02
0.3.6	1 / 0	2026-03-02
0.3.4	1 / 0	2026-03-02
0.3.3	1 / 0	2026-01-24
0.3.2	1 / 0	2026-01-02
0.3.1	1 / 0	2026-01-02
0.3.0	1 / 0	2026-01-01
0.2.83	1 / 0	2025-12-11
0.2.74	1 / 0	2025-12-05
0.2.73	1 / 0	2025-12-01
0.2.72	1 / 0	2025-12-01
0.2.71	1 / 0	2025-11-30
0.2.69	1 / 0	2025-11-03
0.2.67	1 / 0	2025-07-12
0.2.66	1 / 0	2025-07-03
0.2.65	1 / 0	2025-07-01
0.2.64	1 / 0	2025-06-30
0.2.63	1 / 0	2025-06-30
0.2.62	1 / 0	2025-06-23
0.2.61	1 / 0	2025-06-19
0.2.60	1 / 0	2025-06-17
0.2.59	1 / 0	2025-06-17
0.2.58	1 / 0	2025-06-15
0.2.57	1 / 0	2025-06-14
0.2.56	1 / 0	2025-05-31
0.2.55	1 / 0	2025-05-17
0.2.54	1 / 0	2025-05-16
0.2.53	1 / 0	2025-05-15
0.2.52	1 / 0	2025-05-15
0.2.51	1 / 0	2025-05-15
0.2.50	1 / 0	2025-05-15
0.2.49	1 / 0	2025-05-15
0.2.48	1 / 0	2025-05-15
0.2.47	1 / 0	2025-05-13
0.2.46	1 / 0	2025-05-13
0.2.44	1 / 0	2025-05-13
0.2.43	1 / 0	2025-05-11
0.2.42	1 / 0	2025-05-11

v0.3.32

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@wzyjs/next' is 1 edit(s) away from popular package 'nuxt'.

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.