@theia/cli
Theia CLI.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/node-fetch | AI (phantom-deps): Type-only package; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; implicit dependency pattern. | ai | |
| phantom-deps | phantom-dep:@types/chai | AI (phantom-deps): Type-only package; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:http-server | AI (phantom-deps): Referenced in config/scripts, not directly imported; stable pattern for this CLI. | ai | |
| phantom-deps | phantom-dep:@types/mocha | AI (phantom-deps): Type-only package; not directly imported by design. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process imported solely for the patch-package runner; stable pattern for this CLI tool. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require used to load workspace package.json paths — standard monorepo tooling pattern. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @theia/cli; edit-distance match to 'joi' is a false positive. | ai | |
| semgrep | semgrep:child-process-exec | AI (semgrep): Runs patch-package via exec in theia-patch.js — documented, intentional build tooling behavior. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 1.73.1 | 25 / 4 | |
| 1.73.0 | 25 / 4 | |
| 1.72.3 | 25 / 4 | |
| 1.72.2 | 25 / 4 | |
| 1.72.1 | 25 / 4 | |
| 1.72.0 | 25 / 4 | |
| 1.71.2 | 25 / 4 | |
| 1.71.1 | 25 / 4 | |
| 1.71.0 | 25 / 4 | |
| 1.70.2 | 25 / 4 | |
| 1.70.1 | 25 / 4 | |
| 1.70.0 | 25 / 4 | |
| 1.69.0 | 25 / 4 | |
| 1.68.2 | 25 / 4 | |
| 1.68.1 | 25 / 4 | |
| 1.68.0 | 25 / 4 | |
| 1.67.0 | 25 / 4 | |
| 1.66.2 | 25 / 4 | |
| 1.66.1 | 25 / 4 | |
| 1.59.0 | 25 / 4 | |
| 1.58.5 | 25 / 4 | |
| 1.58.4 | 25 / 4 | |
| 1.58.3 | 25 / 4 | |
| 1.58.2 | 25 / 4 | |
| 1.58.1 | 25 / 4 | |
| 1.58.0 | 25 / 4 | |
| 1.57.1 | 25 / 4 | |
| 1.57.0 | 25 / 4 | |
| 1.56.0 | 25 / 4 | |
| 1.55.1 | 25 / 4 | |
| 1.55.0 | 25 / 4 | |
| 1.54.0 | 25 / 4 | |
| 1.53.2 | 25 / 4 | |
| 1.53.1 | 25 / 4 | |
| 1.53.0 | 25 / 4 | |
| 1.51.0 | 25 / 4 | |
| 1.50.1 | 25 / 4 | |
| 1.50.0 | 25 / 4 | |
| 1.49.1 | 25 / 4 | |
| 1.49.0 | 25 / 4 |
v1.73.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.70.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.69.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.68.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.68.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.68.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.67.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (eclipse-theia-bot) on 2025-12-10, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.66.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.66.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
This version was published by a different npm account (eclipse-theia-bot) than the most recent previously approved version (sgraband) on 2025-11-07, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.59.0
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 (sgraband) than the most recent previously approved version (tsmaeder) on 2025-02-27, but sgraband 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.
v1.58.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.4
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 (sgraband) than the most recent previously approved version (tsmaeder) on 2025-03-05, but sgraband 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.
v1.58.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.2
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 (tsmaeder) than the most recent previously approved version (jfaltermeier) on 2025-02-17, but tsmaeder 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.
v1.58.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.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 (jfaltermeier) than the most recent previously approved version (sgraband) on 2024-12-19, but jfaltermeier 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.
v1.57.0
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 (jfaltermeier) than the most recent previously approved version (sgraband) on 2024-12-16, but jfaltermeier 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.
v1.56.0
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 (sgraband) than the most recent previously approved version (jfaltermeier) on 2024-11-28, but sgraband 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.
v1.55.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 (sgraband) than the most recent previously approved version (jfaltermeier) on 2024-12-03, but sgraband 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.
v1.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.54.0
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 (sgraband) than the most recent previously approved version (jfaltermeier) on 2024-09-26, but sgraband 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.
v1.53.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.49.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.