i18next-client
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:reports/coverage/Chrome 53.0 (Mac)/prettify.js | AI (source-diff): This is the well-known Google Code Prettify syntax highlighter (minified), bundled as part of karma/Istanbul HTML coverage reports. Benign test artifact, not malicious code. | ai | |
| source-diff | obfuscated-file:reports/coverage/Firefox 47.0 (Mac)/prettify.js | AI (source-diff): Same Google Code Prettify minified library in coverage report artifacts. Benign test artifact. | ai | |
| source-diff | obfuscated-file:reports/coverage/PhantomJS 1.9 (Mac)/prettify.js | AI (source-diff): Same Google Code Prettify minified library in coverage report artifacts. Benign test artifact. | ai | |
| source-diff | obfuscated-file:reports/coverage/Safari 10.0 (Mac)/prettify.js | AI (source-diff): Same Google Code Prettify minified library in coverage report artifacts. Benign test artifact. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.11.5 | 0 / 11 | |
| 1.11.4 | 0 / 11 | |
| 1.11.3 | 0 / 11 | |
| 1.11.2 | 0 / 11 | |
| 1.11.1 | 0 / 11 | |
| 1.11.0 | 0 / 11 | |
| 1.10.3 | 0 / 11 | |
| 1.10.2 | 0 / 11 | |
| 1.10.1 | 0 / 11 | |
| 1.10.0 | 0 / 11 | |
| 1.9.0 | 0 / 11 | |
| 1.8.2 | 0 / 10 | |
| 1.8.1 | 0 / 10 | |
| 1.8.0 | 0 / 10 | |
| 1.7.7 | 0 / 10 | |
| 1.7.6 | 0 / 10 | |
| 1.7.4 | 0 / 10 |
v1.11.5
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.