@semcore/i18n-unplugin
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Semrush UI-kit monorepo package; no provenance has been a consistent pattern across their releases. | ai | |
| provenance | publisher-changed | AI (provenance): uikit-team is the Semrush UI-kit org account; 41 approved packages and matching org email confirm legitimate transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same org transition; uikit-team has established track record with 41 approved packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by publisher migration from semrushinc to uikit-team; no malicious indicators. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 17.0.0 | 1 / 6 | |
| 16.1.0 | 1 / 6 | |
| 16.0.10 | 1 / 6 | |
| 16.0.9 | 1 / 6 | |
| 16.0.8 | 1 / 6 | |
| 16.0.7 | 1 / 6 | |
| 16.0.6 | 1 / 6 | |
| 16.0.5 | 1 / 6 | |
| 16.0.4 | 1 / 6 | |
| 16.0.3 | 1 / 6 | |
| 16.0.2 | 1 / 6 | |
| 16.0.1 | 1 / 6 | |
| 16.0.0 | 1 / 7 |
v17.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: uikit-team.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.9
2 findingsThis version was published by a different npm account than previous versions on 2025-10-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.