unicode-property-value-aliases
Unicode property value alias mappings in JavaScript format.
Supply chain provenance
Status for the latest visible version.
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
Keywords
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 Mathias Bynens' known transition to Google automation account; consistent across his Unicode package portfolio. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): google-wombot is a known Google automation account for Mathias Bynens' packages; this is a legitimate organizational transition, not a takeover. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 3.9.0 | 0 / 3 | |
| 3.8.0 | 0 / 3 | |
| 3.7.1 | 0 / 3 | |
| 3.7.0 | 0 / 3 | |
| 3.6.0 | 0 / 3 | |
| 3.5.0 | 0 / 3 | |
| 3.4.0 | 0 / 3 | |
| 3.3.0 | 0 / 3 | |
| 3.2.0 | 0 / 3 | |
| 3.1.0 | 0 / 3 | |
| 3.0.0 | 0 / 3 | |
| 2.0.0 | 0 / 3 | |
| 1.2.2 | 0 / 3 | |
| 1.2.1 | 0 / 3 | |
| 1.2.0 | 0 / 3 | |
| 1.1.0 | 0 / 3 | |
| 1.0.4 | 0 / 3 | |
| 1.0.3 | 0 / 3 | |
| 1.0.2 | 0 / 3 | |
| 1.0.1 | 0 / 3 | |
| 1.0.0 | 0 / 3 |
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.