@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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@inlang/rpc | AI (dependencies): Same-org first-party dependency. | ai | |
| source-diff | encoded-string-file:dist/main.js | AI (source-diff): Base64 is @sentry/node's bundled ANR worker script — a documented pattern stable across versions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established 138-version package with SLSA provenance; dormancy flag is not indicative of takeover here. | ai | |
| 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:esbuild-wasm | AI (phantom-deps): Platform-specific binary package; not directly imported but required at runtime. | 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 |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 3.1.15 | 2 / 16 | |
| 3.1.14 | 2 / 17 | |
| 3.1.13 | 2 / 17 | |
| 3.1.12 | 2 / 17 | |
| 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 | |
| 3.0.11 | 2 / 17 | |
| 3.0.10 | 2 / 17 | |
| 3.0.9 | 2 / 17 | |
| 3.0.8 | 2 / 17 | |
| 3.0.7 | 2 / 17 | |
| 3.0.6 | 2 / 17 | |
| 3.0.5 | 2 / 17 | |
| 3.0.4 | 2 / 17 | |
| 3.0.3 | 2 / 17 | |
| 3.0.2 | 2 / 17 | |
| 3.0.1 | 3 / 16 | |
| 3.0.0 | 1 / 18 |
v3.1.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (inlangbot) than the most recent previously approved version (samuelstroschein) on 2025-02-28, but inlangbot is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (inlangbot) than the most recent previously approved version (samuelstroschein) on 2025-02-27, but inlangbot is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.