unicode-9.0.0
JavaScript-compatible Unicode data. Arrays of code points, arrays of symbols, and regular expressions for Unicode v9.0.0’s categories, scripts, blocks, bidi, and other properties.
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 | no-provenance | AI (provenance): Established package by highly reputable publisher (mathiasbynens); lack of Sigstore provenance is not a risk signal for this package. | ai | |
| source-diff | obfuscated-file:Bidi_Paired_Bracket_Type/index.js | AI (source-diff): gzip-compressed Unicode data tables embedded as Buffer byte arrays — standard data packaging technique for this Unicode data package, not obfuscation. | ai | |
| source-diff | obfuscated-file:Line_Break/Ideographic/code-points.js | AI (source-diff): gzip-compressed Unicode data tables embedded as Buffer byte arrays — standard data packaging for this Unicode data package. | ai | |
| source-diff | obfuscated-file:Line_Break/Ideographic/symbols.js | AI (source-diff): gzip-compressed Unicode data tables embedded as Buffer byte arrays — standard data packaging for this Unicode data package. | ai | |
| source-diff | obfuscated-file:Line_Break/Alphabetic/code-points.js | AI (source-diff): gzip-compressed Unicode data tables embedded as Buffer byte arrays — standard data packaging for this Unicode data package. | ai | |
| source-diff | obfuscated-file:Line_Break/Alphabetic/regex.js | AI (source-diff): Long Unicode regex character class — exactly what a Unicode data package exports; not obfuscation. | ai | |
| source-diff | obfuscated-file:Line_Break/Alphabetic/symbols.js | AI (source-diff): gzip-compressed Unicode data tables embedded as Buffer byte arrays — standard data packaging for this Unicode data package. | ai | |
| source-diff | obfuscated-file:Line_Break/Combining_Mark/code-points.js | AI (source-diff): gzip-compressed Unicode data tables embedded as Buffer byte arrays — standard data packaging for this Unicode data package. | ai | |
| source-diff | obfuscated-file:Line_Break/Combining_Mark/symbols.js | AI (source-diff): gzip-compressed Unicode data tables embedded as Buffer byte arrays — standard data packaging for this Unicode data package. | ai | |
| source-diff | obfuscated-file:Line_Break/Complex_Context/code-points.js | AI (source-diff): gzip-compressed Unicode data tables embedded as Buffer byte arrays — standard data packaging for this Unicode data package. | ai | |
| source-diff | obfuscated-file:Line_Break/Complex_Context/symbols.js | AI (source-diff): gzip-compressed Unicode data tables embedded as Buffer byte arrays — standard data packaging for this Unicode data package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Unicode data packages inherently contain hundreds of data files covering categories, scripts, blocks, etc. Large file counts are expected for this package type. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): unicode-9.0.0 is a static Unicode spec data package; long dormancy between releases is expected and normal for this package type. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.7.5 | 0 / 0 | |
| 0.7.4 | 0 / 0 | |
| 0.7.3 | 0 / 0 | |
| 0.7.2 | 0 / 0 | |
| 0.7.1 | 0 / 0 | |
| 0.7.0 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v0.7.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mathias.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
11 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
11 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.