@inlang/cli
--- title: inlang CLI - Localization Automation for CI/CD description: Automate translation workflows with machine translation, validation, and CI/CD integration. Supports JSON, i18next, next-intl, and more. og:image: https://cdn.jsdelivr.net/gh/opral/inl
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@inlang/rpc | AI (phantom-deps): Same org scope; likely used transitively or bundled in dist output. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @inlang/cli is an established i18n CLI; Levenshtein match to 'joi' is coincidental and not a typosquat. | ai | |
| phantom-deps | phantom-dep:@inlang/sdk | AI (phantom-deps): Same org scope; used as a runtime dep in the built output, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:esbuild-wasm | AI (phantom-deps): Platform-specific binary package; not directly imported but required at runtime. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.1.11 | 2 / 17 | |
| 3.1.10 | 2 / 17 | |
| 3.1.9 | 2 / 17 | |
| 3.1.8 | 2 / 17 | |
| 3.1.7 | 2 / 17 | |
| 3.1.6 | 2 / 17 | |
| 3.1.5 | 2 / 17 | |
| 3.1.4 | 2 / 17 | |
| 3.1.3 | 2 / 17 | |
| 3.1.2 | 2 / 17 | |
| 3.1.1 | 3 / 16 | |
| 3.1.0 | 3 / 16 | |
| 3.0.12 | 2 / 17 |
v3.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.