unicode-property-aliases MIT 15 versions

unicode-property-aliases

npm Repository Homepage

Unicode property alias mappings in JavaScript format.

15

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

unicodeunicode-dataaliasaliasesproperty alias

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from mathias to google-wombot reflects a legitimate Google/Mathias Bynens organizational handoff; google-wombot manages many of Mathias's Unicode packages with a strong approval track record.	ai	2026/04/24

Versions (showing 15 of 15)

Version	Deps	Published
2.1.0	0 / 2	2025-08-28
2.0.0	0 / 2	2024-09-12
1.7.0	0 / 2	2024-09-12
1.6.2	0 / 2	2024-08-26
1.6.1	0 / 2	2023-08-17
1.6.0	0 / 2	2022-09-14
1.5.1	0 / 2	2021-07-29
1.5.0	0 / 2	2020-03-11
1.4.0	0 / 2	2019-03-05
1.3.0	0 / 2	2018-02-22
1.2.0	0 / 2	2018-02-18
1.1.1	0 / 2	2017-03-07
1.1.0	0 / 2	2016-06-03
1.0.1	0 / 2	2016-05-30
1.0.0	0 / 2	2016-05-21

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

2 findings

HIGH Publisher changed: mathias → google-wombot (on 2024-09-12) provenance

This version was published by a different npm account than previous versions on 2024-09-12. 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.

v1.7.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: google-wombot → mathias (on 2024-09-12) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2024-09-12. This could indicate a legitimate maintainer transition or an account compromise.

v1.6.2

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mathias → google-wombot (on 2021-07-29) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-07-29. This could indicate a legitimate maintainer transition or an account compromise.

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

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

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.