@theia/external-terminal
Theia - External Terminal Extension
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): External terminal extension legitimately uses child_process to spawn terminal emulators; stable pattern across versions. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): Spawning terminal processes is the core purpose of this extension; not a security concern. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.72.1 | 4 / 1 | |
| 1.72.0 | 4 / 1 | |
| 1.71.2 | 4 / 1 | |
| 1.71.1 | 4 / 1 | |
| 1.71.0 | 4 / 1 | |
| 1.70.2 | 4 / 1 | |
| 1.70.1 | 4 / 1 | |
| 1.70.0 | 4 / 1 | |
| 1.68.2 | 4 / 1 | |
| 1.68.1 | 4 / 1 | |
| 1.64.2 | 4 / 1 | |
| 1.62.1 | 4 / 1 |
v1.72.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.72.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.71.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.71.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.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.64.2
2 findingsThis version was published by a different npm account than previous versions on 2025-10-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.