unicode-segmenter
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:bundle/grapheme.js | AI (source-diff): Bundle file is esbuild output with readable source comments; long lines are base-36 encoded Unicode range tables, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:bundle/intl-adapter.js | AI (source-diff): Bundle file is esbuild output with readable source comments; long lines are base-36 encoded Unicode range tables, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:bundle/intl-polyfill.js | AI (source-diff): Bundle file is esbuild output with readable source comments; long lines are base-36 encoded Unicode range tables, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:bundle/general.js | AI (source-diff): Bundle file is esbuild output with readable source comments; long lines are base-36 encoded Unicode range tables, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:bundle/index.js | AI (source-diff): Bundle file is esbuild output with readable source comments; long lines are base-36 encoded Unicode range tables, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | encoded-string-file:_grapheme_data.js | AI (source-diff): Same as _grapheme_data.cjs: legitimate Unicode table encoding, not a malicious payload. Stable false positive for this package. | ai | |
| source-diff | encoded-string-file:_grapheme_data.cjs | AI (source-diff): The long string is a compact run-length encoding of Unicode grapheme category ranges passed to decodeUnicodeData(). This is the package's documented data format, not obfuscation. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.16.0 | 0 / 28 | |
| 0.15.0 | 0 / 27 | |
| 0.14.5 | 0 / 27 | |
| 0.14.4 | 0 / 27 | |
| 0.14.3 | 0 / 27 | |
| 0.14.2 | 0 / 27 | |
| 0.14.1 | 0 / 27 | |
| 0.14.0 | 0 / 28 | |
| 0.13.2 | 0 / 26 | |
| 0.13.1 | 0 / 26 | |
| 0.13.0 | 0 / 26 |
v0.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
8 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.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.5
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.4
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.3
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.