@intlayer/cli
Provides uniform command-line interface scripts for Intlayer, used in packages like intlayer-cli and intlayer.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @intlayer/cli package; Levenshtein match against 'joi' is a false positive for this established monorepo. | ai | |
| phantom-deps | phantom-dep:@intlayer/remote-dictionaries-entry | AI (phantom-deps): Same-org sibling dep; may be re-exported or used indirectly within the monorepo build. | ai |
Versions (showing 9 of 109)
| Version | Deps | Published |
|---|---|---|
| 7.1.8 | 10 / 9 | |
| 7.1.7 | 10 / 9 | |
| 7.1.6 | 10 / 9 | |
| 7.1.5 | 10 / 9 | |
| 7.0.8 | 10 / 9 | |
| 7.0.7 | 10 / 9 | |
| 7.0.6 | 10 / 9 | |
| 7.0.5 | 10 / 9 | |
| 7.0.4 | 10 / 9 |
v7.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.