regenerate-unicode-properties
Regenerate sets for Unicode properties and values.
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): New files are Unicode property data files; adding many is expected when updating Unicode standard coverage. | ai | |
| source-diff | obfuscated-file:Binary_Property/Grapheme_Extend.js | AI (source-diff): Long lines are Unicode code point hex arrays passed to regenerate() — the core data format of this package, not obfuscation. | ai | |
| source-diff | obfuscated-file:Binary_Property/ID_Continue.js | AI (source-diff): Long lines are Unicode code point hex arrays passed to regenerate() — the core data format of this package, not obfuscation. | ai | |
| source-diff | obfuscated-file:Binary_Property/ID_Start.js | AI (source-diff): Long lines are Unicode code point hex arrays passed to regenerate() — the core data format of this package, not obfuscation. | ai | |
| source-diff | obfuscated-file:Binary_Property/Changes_When_Uppercased.js | AI (source-diff): Long lines are Unicode code point hex arrays passed to regenerate() — the core data format of this package, not obfuscation. | ai | |
| source-diff | obfuscated-file:Binary_Property/Changes_When_Titlecased.js | AI (source-diff): Long lines are Unicode code point hex arrays passed to regenerate() — the core data format of this package, not obfuscation. | ai | |
| source-diff | obfuscated-file:Binary_Property/Changes_When_NFKC_Casefolded.js | AI (source-diff): Long lines are Unicode code point hex arrays passed to regenerate() — the core data format of this package, not obfuscation. | ai | |
| source-diff | obfuscated-file:Binary_Property/Changes_When_Lowercased.js | AI (source-diff): Long lines are Unicode code point hex arrays passed to regenerate() — the core data format of this package, not obfuscation. | ai | |
| source-diff | obfuscated-file:Binary_Property/Changes_When_Casefolded.js | AI (source-diff): Long lines are Unicode code point hex arrays passed to regenerate() — the core data format of this package, not obfuscation. | ai | |
| source-diff | obfuscated-file:Binary_Property/Case_Ignorable.js | AI (source-diff): Long lines are Unicode code point hex arrays passed to regenerate() — the core data format of this package, not obfuscation. | ai | |
| source-diff | obfuscated-file:Binary_Property/XID_Continue.js | AI (source-diff): Long lines are Unicode code point hex arrays passed to regenerate() — the core data format of this package, not obfuscation. | ai | |
| source-diff | obfuscated-file:Binary_Property/XID_Start.js | AI (source-diff): Long lines are Unicode code point hex arrays passed to regenerate() — the core data format of this package, not obfuscation. | ai | |
| source-diff | obfuscated-file:Binary_Property/Grapheme_Base.js | AI (source-diff): Long lines are Unicode code point hex arrays passed to regenerate() — the core data format of this package, not obfuscation. | ai | |
| dependencies | unvetted-dep:regenerate | AI (dependencies): regenerate is the core dependency this package is explicitly built around, authored by the same developer (Mathias Bynens). Stable and legitimate for this package. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 10.2.2 | 1 / 3 | |
| 10.2.1 | 1 / 3 | |
| 10.2.0 | 1 / 5 | |
| 10.1.1 | 1 / 5 | |
| 10.1.0 | 1 / 5 | |
| 10.0.1 | 1 / 5 | |
| 10.0.0 | 1 / 5 | |
| 9.0.0 | 1 / 5 | |
| 8.2.0 | 1 / 5 | |
| 8.1.0 | 1 / 5 | |
| 8.0.2 | 1 / 5 | |
| 8.0.1 | 1 / 5 | |
| 8.0.0 | 1 / 5 | |
| 7.0.0 | 1 / 5 | |
| 6.0.0 | 1 / 5 | |
| 5.1.3 | 1 / 6 | |
| 5.1.2 | 1 / 6 | |
| 5.1.1 | 1 / 6 | |
| 5.1.0 | 1 / 6 | |
| 5.0.7 | 1 / 6 | |
| 5.0.6 | 1 / 6 | |
| 5.0.5 | 1 / 6 | |
| 5.0.4 | 1 / 5 | |
| 5.0.3 | 1 / 5 | |
| 5.0.2 | 1 / 5 | |
| 5.0.1 | 1 / 5 | |
| 5.0.0 | 1 / 5 | |
| 4.0.2 | 1 / 5 | |
| 4.0.1 | 1 / 5 | |
| 4.0.0 | 1 / 4 | |
| 3.0.0 | 1 / 4 | |
| 2.0.0 | 1 / 4 | |
| 1.0.0 | 1 / 4 |
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
13 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
13 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.