@unicode/unicode-13.0.0
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:Script_Extensions/Unknown/regex.js | AI (source-diff): Long-line regex files are the expected output format for Unicode data packages; not obfuscation. | ai | |
| source-diff | obfuscated-file:Script/Unknown/regex.js | AI (source-diff): Long-line regex files are the expected output format for Unicode data packages; not obfuscation. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): All base64-decode findings are compressed Unicode property data tables decoded via Node's built-in zlib — a standard, benign data-compression pattern for this package. No network access or eval involved. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.6.16 | 0 / 0 | |
| 1.6.12 | 0 / 0 | |
| 1.6.11 | 0 / 0 | |
| 1.6.10 | 0 / 0 | |
| 1.6.9 | 0 / 0 | |
| 1.6.7 | 0 / 0 | |
| 1.6.6 | 0 / 0 |
v1.6.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.12
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.