nuxt-i18n-micro
Nuxt I18n Micro is a lightweight, high-performance internationalization module for Nuxt, designed to handle multi-language support with minimal overhead, fast build times, and efficient runtime performance.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:nuxt-i18n-micro-core | AI (dependencies): First-party monorepo sub-package from same author; stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:nuxt-i18n-micro-test-utils | AI (phantom-deps): Test utility referenced in config only; not a runtime import concern. | ai | |
| dependencies | unvetted-dep:nuxt-i18n-micro-test-utils | AI (dependencies): First-party monorepo sub-package from same author; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:nuxt-i18n-micro-types | AI (dependencies): First-party monorepo sub-package from same author; stable pattern across versions. | ai | |
| source-diff | obfuscated-file:dist/client/_nuxt/B-cq5x_h.js | AI (source-diff): Standard Vite/Nuxt minified client bundle; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/_nuxt/BCTbvRLO.js | AI (source-diff): Standard Vite/Nuxt minified client bundle; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/_nuxt/BNXusRXY.js | AI (source-diff): Standard Vite/Nuxt minified client bundle; not malicious obfuscation. | ai | |
| dependencies | unvetted-dep:@i18n-micro/types | AI (dependencies): Own monorepo scoped package; stable false positive for this publisher. | ai | |
| dependencies | unvetted-dep:@i18n-micro/core | AI (dependencies): Own monorepo scoped package; stable false positive for this publisher. | ai | |
| dependencies | unvetted-dep:@i18n-micro/path-strategy | AI (dependencies): Own monorepo scoped package; stable false positive for this publisher. | ai | |
| dependencies | unvetted-dep:@i18n-micro/test-utils | AI (dependencies): Own monorepo scoped package; stable false positive for this publisher. | ai | |
| dependencies | unvetted-dep:@i18n-micro/route-strategy | AI (dependencies): Own monorepo scoped package; stable false positive for this publisher. | ai | |
| phantom-deps | phantom-dep:@i18n-micro/test-utils | AI (phantom-deps): Test utility declared in config but not directly imported at runtime; stable false positive for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 3.19.0 | 12 / 21 | |
| 3.18.3 | 10 / 21 | |
| 3.18.2 | 10 / 21 | |
| 3.18.1 | 10 / 21 | |
| 3.17.5 | 10 / 21 | |
| 3.17.0 | 10 / 21 | |
| 3.16.0 | 10 / 21 | |
| 3.15.3 | 10 / 21 | |
| 3.8.1 | 10 / 21 | |
| 3.6.0 | 10 / 21 | |
| 3.5.0 | 10 / 21 | |
| 3.4.0 | 10 / 20 | |
| 3.3.0 | 10 / 21 | |
| 3.2.3 | 10 / 17 | |
| 3.2.1 | 10 / 17 | |
| 3.1.0 | 10 / 17 | |
| 2.16.3 | 8 / 17 | |
| 2.16.2 | 8 / 17 | |
| 2.16.1 | 8 / 17 | |
| 2.15.2 | 8 / 17 | |
| 2.15.1 | 8 / 17 | |
| 2.15.0 | 9 / 17 | |
| 2.14.1 | 9 / 17 | |
| 2.13.0 | 9 / 17 | |
| 2.12.1 | 9 / 17 | |
| 2.12.0 | 9 / 17 | |
| 2.11.0 | 9 / 17 | |
| 2.10.0 | 9 / 17 | |
| 2.8.0 | 9 / 17 | |
| 2.7.0 | 9 / 17 | |
| 2.3.0 | 9 / 17 | |
| 2.2.0 | 9 / 17 |
v3.19.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.3
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.2
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.