@zxcvbn-ts/language-en
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 | obfuscated-file:dist/commonWords.json.cjs | AI (source-diff): Compressed English dictionary word list for password strength estimation; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/firstnames.json.cjs | AI (source-diff): Compressed English first-names dictionary; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lastnames.json.cjs | AI (source-diff): Compressed English last-names dictionary; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/wikipedia.json.cjs | AI (source-diff): Compressed Wikipedia common-words dictionary; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/commonWords.json.mjs | AI (source-diff): ESM variant of compressed common-words dictionary; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/firstnames.json.mjs | AI (source-diff): ESM variant of compressed first-names dictionary; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lastnames.json.mjs | AI (source-diff): ESM variant of compressed last-names dictionary; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/wikipedia.json.mjs | AI (source-diff): ESM variant of compressed Wikipedia dictionary; not obfuscation. | ai | |
| source-diff | encoded-string-file:dist/zxcvbn-ts.js | AI (source-diff): Encoded strings are compressed dictionary data for password strength checking. | ai |
v4.1.0
10 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.
Modified file contains 42 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.