@i18n-micro/path-strategy
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/base-strategy.cjs | AI (source-diff): Minified Vite CJS build output; content is URL/path utilities with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/common.cjs | AI (source-diff): Minified Vite CJS build output; content is i18n routing logic with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/base-strategy-BNdOdpRE.cjs | AI (source-diff): Minified Vite bundle output; sample shows URL-encoding utilities, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/base-strategy-iCda2UF-.cjs | AI (source-diff): Minified Vite bundle output; content is URL encoding utilities matching declared ufo dependency, no malicious code. | ai | |
| source-diff | obfuscated-file:dist/base-strategy-BuHeTv1K.cjs | AI (source-diff): Minified Vite/Rollup bundle; sample shows standard ufo URL helpers, not obfuscation or malware. | ai | |
| phantom-deps | phantom-dep:ufo | AI (phantom-deps): ufo is a declared runtime dep bundled into dist; not directly imported in source files by design. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.3.2 | 1 / 5 | |
| 1.3.0 | 1 / 2 | |
| 1.2.0 | 2 / 2 | |
| 1.1.3 | 2 / 2 | |
| 1.1.2 | 2 / 2 | |
| 1.1.1 | 2 / 2 | |
| 1.0.3 | 2 / 2 | |
| 1.0.1 | 2 / 2 | |
| 1.0.0 | 2 / 2 |
v1.3.2
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
2 findingsNewly 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.1.3
2 findingsNewly 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.1.2
2 findingsNewly 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.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.