@microsoft/ts-command-line
(Please use "@rushstack/ts-command-line" instead.)
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @types/argparse is the TypeScript type definitions for the already-present argparse dependency — a benign, expected companion package with no security implications. | ai | |
| phantom-deps | phantom-dep:@types/argparse | AI (phantom-deps): @types/argparse is a TypeScript type definition package; not directly imported but used for type resolution. Benign and expected pattern. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a TypeScript type package loaded by convention, not direct import. This is expected for TypeScript packages and stable across versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Empty description is consistent with a placeholder/namespace reservation version; not a malicious signal for this established Microsoft package. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is a namespace reservation pattern used by Microsoft for this scoped package; not indicative of malicious intent given publisher track record and package age. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): This is a deprecation stub package; postinstall is used to display a migration notice. Consistent with Microsoft/Rushstack's pattern for deprecated packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is an intentional deprecation stub redirecting users to @rushstack/ts-command-line. Minimal payload, no deps, and no repo URL are expected for this type of package. | ai |
Versions (showing 76 of 76)
| Version | Deps | Published |
|---|---|---|
| 5.0.1 | 0 / 0 | |
| 5.0.0 | 0 / 0 | |
| 4.3.10 | 3 / 6 | |
| 4.3.9 | 3 / 6 | |
| 4.3.8 | 3 / 6 | |
| 4.3.7 | 3 / 6 | |
| 4.3.6 | 3 / 6 | |
| 4.3.5 | 3 / 6 | |
| 4.3.4 | 3 / 6 | |
| 4.3.3 | 3 / 5 | |
| 4.3.2 | 3 / 5 | |
| 4.3.1 | 3 / 5 | |
| 4.3.0 | 2 / 6 | |
| 4.2.8 | 4 / 4 | |
| 4.2.7 | 4 / 4 | |
| 4.2.6 | 4 / 5 | |
| 4.2.5 | 4 / 5 | |
| 4.2.4 | 4 / 5 | |
| 4.2.3 | 4 / 5 | |
| 4.2.2 | 4 / 5 | |
| 4.2.1 | 4 / 3 | |
| 4.2.0 | 4 / 3 | |
| 4.1.0 | 4 / 3 | |
| 4.0.0 | 4 / 3 | |
| 3.1.1 | 4 / 4 | |
| 3.1.0 | 4 / 5 | |
| 3.0.7 | 4 / 5 | |
| 3.0.6 | 4 / 5 | |
| 3.0.5 | 4 / 5 | |
| 3.0.4 | 4 / 5 | |
| 3.0.3 | 4 / 5 | |
| 3.0.2 | 4 / 5 | |
| 3.0.1 | 4 / 5 | |
| 2.3.10 | 4 / 5 | |
| 2.3.9 | 4 / 5 | |
| 2.3.8 | 4 / 5 | |
| 2.3.7 | 4 / 5 | |
| 2.3.6 | 4 / 5 | |
| 2.3.5 | 4 / 5 | |
| 2.3.4 | 4 / 5 | |
| 2.3.3 | 4 / 5 | |
| 2.3.2 | 4 / 5 | |
| 2.3.1 | 4 / 5 | |
| 2.3.0 | 4 / 5 | |
| 2.2.14 | 4 / 5 | |
| 2.2.13 | 4 / 5 | |
| 2.2.12 | 4 / 5 | |
| 2.2.11 | 4 / 5 | |
| 2.2.10 | 4 / 5 | |
| 2.2.9 | 4 / 5 | |
| 2.2.8 | 4 / 5 | |
| 2.2.7 | 4 / 5 | |
| 2.2.6 | 4 / 5 | |
| 2.2.5 | 4 / 5 | |
| 2.2.4 | 4 / 5 | |
| 2.2.3 | 4 / 5 | |
| 2.2.2 | 4 / 5 | |
| 2.2.1 | 4 / 5 | |
| 2.2.0 | 3 / 5 | |
| 2.1.4 | 3 / 5 | |
| 2.1.3 | 3 / 5 | |
| 2.1.2 | 3 / 5 | |
| 2.1.1 | 3 / 5 | |
| 2.1.0 | 3 / 5 | |
| 2.0.7 | 3 / 5 | |
| 2.0.6 | 3 / 6 | |
| 2.0.5 | 3 / 6 | |
| 2.0.4 | 3 / 6 | |
| 2.0.3 | 3 / 5 | |
| 2.0.2 | 3 / 5 | |
| 2.0.1 | 3 / 5 | |
| 2.0.0 | 3 / 5 | |
| 1.1.1 | 3 / 4 | |
| 1.1.0 | 2 / 4 | |
| 1.0.1 | 2 / 4 | |
| 0.0.0 | 0 / 0 |
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. 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.