unicode-loose-match MIT 20 versions

unicode-loose-match

npm Repository Homepage

A JavaScript implementation of Unicode loose matching.

20

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

mathiasgoogle-wombot

Keywords

unicodeloose matching

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): google-wombot is the standard Google automation account used by Mathias Bynens for Unicode packages; this transition is expected and consistent across the ecosystem.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): google-wombot addition is a known legitimate pattern for Mathias Bynens Unicode packages published under Google's npm automation account.	ai	2026/04/23

Versions (showing 20 of 20)

Version	Deps	Published
2.8.1	0 / 5	2025-08-28
2.8.0	0 / 5	2025-08-28
2.7.0	0 / 5	2024-08-26
2.6.0	0 / 5	2023-08-18
2.5.0	0 / 5	2018-06-07
2.4.0	0 / 5	2018-02-22
2.3.0	0 / 5	2018-02-18
2.2.1	0 / 5	2017-09-10
2.2.0	0 / 5	2016-06-21
2.1.1	0 / 5	2016-06-03
2.1.0	0 / 5	2016-06-03
2.0.7	0 / 5	2016-05-30
2.0.6	0 / 5	2016-05-26
2.0.5	0 / 5	2016-05-26
2.0.4	0 / 5	2016-05-25
2.0.3	0 / 5	2016-05-25
2.0.2	0 / 5	2016-05-25
2.0.1	0 / 5	2016-05-22
2.0.0	3 / 3	2016-05-21
1.0.0	0 / 3	2016-05-20

v2.8.1

2 findings

HIGH Publisher changed: mathias → google-wombot (on 2025-08-28) provenance

This version was published by a different npm account than previous versions on 2025-08-28. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.8.0

1 finding

LOW No provenance attestation provenance

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

v2.7.0

1 finding

LOW No provenance attestation provenance

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

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.0.0

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.