← Home

@hanzogui/text

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

artemis-primezeekay

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:next AI (typosquat): Scoped @hanzogui org package; not a typosquat of 'next', Levenshtein match is coincidental. ai
typosquat typosquat.levenshtein:nuxt AI (typosquat): Scoped @hanzogui org package; not a typosquat of 'nuxt'. ai
typosquat typosquat.levenshtein:jest AI (typosquat): Scoped @hanzogui org package; not a typosquat of 'jest'. ai
phantom-deps phantom-dep:@hanzogui/web AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for org-internal packages. ai
phantom-deps phantom-dep:@hanzogui/helpers AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for org-internal packages. ai
phantom-deps phantom-dep:@hanzogui/get-font-sized AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for org-internal packages. ai

Versions (showing 9 of 9)

Version Deps Published
7.0.0 3 / 2
3.0.2 3 / 2
3.0.1 3 / 2
3.0.0 3 / 2
2.0.8 3 / 2
2.0.7 3 / 2
2.0.5 3 / 2
2.0.4 3 / 2
2.0.0 3 / 2

v3.0.2

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

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

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.

v3.0.1

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

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

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.

v3.0.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

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

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.

v2.0.8

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

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

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.

v2.0.7

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

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

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.

v2.0.5

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

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

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.

v2.0.4

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

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

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.

v2.0.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

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

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.