@lazy-cjk/util ISC 15 versions

@lazy-cjk/util

npm Repository Homepage

15

Versions

ISC

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

bluelovers

Keywords

charcharactercharacterschinesecjkcjk-convregexp-cjkcncn2twconvconversionconvertgreedyhanjahanzijapanesejp2zhsjp2zhtkanjinode-novelregexregexpregularregular expressionsimplifiedslugifystr-utiltabletraditionaltransformtwtw2cnunicodeutilwordszhzh-cnzh-twzh2jpzhszht

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:uuid	AI (typosquat): Scoped CJK utility package; name similarity to uuid is coincidental, not impersonation.	ai	2026/04/29

Versions (showing 15 of 15)

Version	Deps	Published
1.0.20	2 / 0	2024-08-24
1.0.19	2 / 0	2024-01-29
1.0.18	2 / 0	2022-10-16
1.0.17	2 / 0	2022-02-04
1.0.14	2 / 0	2021-08-13
1.0.13	2 / 0	2021-07-26
1.0.12	2 / 0	2021-07-09
1.0.9	2 / 0	2021-06-21
1.0.7	1 / 0	2020-06-26
1.0.6	1 / 0	2020-06-11
1.0.5	1 / 0	2020-06-09
1.0.4	1 / 0	2020-06-07
1.0.3	1 / 0	2020-06-06
1.0.2	1 / 0	2020-06-03
1.0.1	1 / 0	2020-05-28

v1.0.19

1 finding

LOW No provenance attestation provenance

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

v1.0.18

1 finding

LOW No provenance attestation provenance

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

v1.0.17

1 finding

LOW No provenance attestation provenance

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

v1.0.14

1 finding

LOW No provenance attestation provenance

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

v1.0.13

1 finding

LOW No provenance attestation provenance

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

v1.0.12

1 finding

LOW No provenance attestation provenance

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

v1.0.9

1 finding

LOW No provenance attestation provenance

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

v1.0.7

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.2

1 finding

LOW No provenance attestation provenance

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

v1.0.1

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.