@steedos/i18n
- 此包用于系统国际化翻译功能
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Long-running monorepo package; missing description is a stable characteristic, not a malice indicator. | ai | |
| dependencies | unvetted-dep:i18next-sprintf-postprocessor | AI (dependencies): i18next-sprintf-postprocessor is a small, stable sprintf post-processor for i18next; no known advisories and consistent use across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of the large, long-lived @steedos monorepo; sparse metadata is typical for internal scoped packages. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with 1549 versions; lack of provenance is consistent across the package history. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.0.14 | 4 / 1 | |
| 3.0.13 | 4 / 1 | |
| 3.0.11 | 4 / 1 | |
| 3.0.10 | 4 / 1 | |
| 3.0.6 | 4 / 1 | |
| 3.0.4 | 4 / 1 | |
| 3.0.3 | 4 / 1 | |
| 2.7.29 | 4 / 1 | |
| 2.7.27 | 4 / 1 | |
| 2.7.23 | 4 / 1 |
v3.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.