@nuxtjs/i18n
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Published via GitHub Actions with SLSA provenance; gitHead absence is a CI config change, not a threat. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with 115 versions; dormancy reflects normal release cadence variation. | ai | |
| dependencies | unvetted-dep:@intlify/utils | AI (dependencies): First-party @intlify ecosystem dep from same maintainer org; stable for this package. | ai | |
| dependencies | unvetted-dep:@intlify/unplugin-vue-i18n | AI (dependencies): First-party @intlify ecosystem dep from same maintainer org; stable for this package. | ai | |
| dependencies | unvetted-dep:@intlify/h3 | AI (dependencies): First-party @intlify ecosystem dep from same maintainer org; stable for this package. | ai | |
| dependencies | unvetted-dep:@miyaneee/rollup-plugin-json5 | AI (dependencies): Build-time rollup plugin for JSON5 support; no malicious indicators. | ai | |
| dependencies | unvetted-dep:nuxt-define | AI (dependencies): Utility dep used by Nuxt module ecosystem; no malicious indicators. | ai | |
| dependencies | unvetted-dep:@intlify/core | AI (dependencies): First-party @intlify ecosystem dep from same maintainer org; stable for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 10.4.0 | 26 / 23 | |
| 10.3.0 | 26 / 22 | |
| 10.2.4 | 27 / 22 | |
| 10.2.3 | 28 / 21 | |
| 10.2.1 | 28 / 21 | |
| 10.2.0 | 28 / 21 | |
| 10.1.2 | 28 / 21 | |
| 10.1.1 | 29 / 26 | |
| 10.1.0 | 29 / 32 | |
| 10.0.6 | 28 / 32 | |
| 10.0.5 | 28 / 32 | |
| 10.0.4 | 28 / 32 | |
| 10.0.3 | 28 / 34 | |
| 10.0.2 | 28 / 34 | |
| 10.0.1 | 28 / 34 | |
| 10.0.0 | 28 / 34 |
v10.4.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: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.