@tsslint/cli
Command-line runner for TSSLint. Lints TypeScript projects — and Vue / Vue Vine / MDX / Astro / TS Macro projects via Volar language plugins — in CI or from the terminal.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@tsslint/types | AI (phantom-deps): Same-org dep used transitively; phantom-dep false positive for this monorepo package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @tsslint/cli; Levenshtein match to 'joi' is a false positive with no brand similarity. | ai | |
| phantom-deps | phantom-dep:@tsslint/config | AI (phantom-deps): Same-org first-party dep; phantom detection is a false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.1.3 | 7 / 0 | |
| 3.1.2 | 7 / 0 | |
| 3.1.1 | 7 / 0 | |
| 3.1.0 | 6 / 0 | |
| 3.0.4 | 7 / 0 | |
| 3.0.3 | 7 / 0 | |
| 3.0.2 | 7 / 0 | |
| 3.0.1 | 7 / 0 | |
| 3.0.0 | 7 / 0 |
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.