@theia/task
Theia - Task extension. This extension adds support for executing raw or terminal processes in the backend.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@theia/variable-resolver | AI (dependencies): Sibling @theia/* monorepo package at matching version. | ai | |
| dependencies | unvetted-dep:@theia/filesystem | AI (dependencies): Sibling @theia/* monorepo package at matching version. | ai | |
| dependencies | unvetted-dep:@theia/userstorage | AI (dependencies): Sibling @theia/* monorepo package at matching version. | ai | |
| dependencies | unvetted-dep:@theia/core | AI (dependencies): Sibling @theia/* monorepo package at matching version; not an independent risk. | ai | |
| dependencies | unvetted-dep:@theia/editor | AI (dependencies): Sibling @theia/* monorepo package at matching version. | ai | |
| dependencies | unvetted-dep:@theia/monaco | AI (dependencies): Sibling @theia/* monorepo package at matching version. | ai | |
| dependencies | unvetted-dep:@theia/markers | AI (dependencies): Sibling @theia/* monorepo package at matching version. | ai | |
| dependencies | unvetted-dep:@theia/process | AI (dependencies): Sibling @theia/* monorepo package at matching version. | ai | |
| dependencies | unvetted-dep:@theia/terminal | AI (dependencies): Sibling @theia/* monorepo package at matching version. | ai | |
| dependencies | unvetted-dep:@theia/workspace | AI (dependencies): Sibling @theia/* monorepo package at matching version. | ai | |
| semgrep | semgrep:dll-hijacking-commands | AI (semgrep): rundll32.exe used as a Windows no-op in test fixtures, not actual DLL side-loading; stable false positive for this package. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Task runner intentionally inherits process.env to pass environment to spawned tasks; standard pattern for this package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.72.2 | 16 / 1 | |
| 1.72.1 | 16 / 1 | |
| 1.72.0 | 16 / 1 | |
| 1.71.2 | 16 / 1 | |
| 1.71.1 | 16 / 1 | |
| 1.70.2 | 16 / 1 | |
| 1.70.1 | 16 / 1 | |
| 1.70.0 | 16 / 1 | |
| 1.69.0 | 15 / 1 | |
| 1.66.2 | 15 / 1 | |
| 1.66.1 | 15 / 1 | |
| 1.66.0 | 15 / 1 | |
| 1.65.2 | 15 / 1 | |
| 1.65.0 | 15 / 1 | |
| 1.64.2 | 15 / 1 | |
| 1.64.1 | 15 / 1 | |
| 1.64.0 | 15 / 1 | |
| 1.63.3 | 15 / 1 | |
| 1.63.2 | 15 / 1 | |
| 1.63.1 | 15 / 1 | |
| 1.63.0 | 15 / 1 | |
| 1.62.2 | 15 / 1 | |
| 1.62.1 | 15 / 1 | |
| 1.62.0 | 15 / 1 | |
| 1.61.1 | 15 / 1 | |
| 1.61.0 | 15 / 1 |
v1.72.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.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
5 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/eclipse-theia/theia/blob/3b413470b0f990dc0d6e4287da02a6b6e21d3239/lib/node/process/process-task-runner.js#L80 78 | // new process, so e.g. we can re-use the system path 79 | if (options) { > 80 | options.env = { 81 | ...process.env, 82 | ...(options.env || {})
DLL side-loading command detected — potential DLL hijacking Source: https://github.com/eclipse-theia/theia/blob/3b413470b0f990dc0d6e4287da02a6b6e21d3239/lib/node/task-server.slow-spec.js#L39 37 | const bogusCommand = 'thisisnotavalidcommand'; 38 | const commandUnixNoop = 'true'; > 39 | const commandWindowsNoop = 'rundll32.exe'; 40 | /** Expects argv to be ['a', 'b', 'c'] */ 41 | const script0 = './test-arguments-0.js';
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/eclipse-theia/theia/blob/3b413470b0f990dc0d6e4287da02a6b6e21d3239/src/node/process/process-task-runner.ts#L121 119 | // new process, so e.g. we can re-use the system path 120 | if (options) { > 121 | options.env = { 122 | ...process.env, 123 | ...(options.env || {})
DLL side-loading command detected — potential DLL hijacking Source: https://github.com/eclipse-theia/theia/blob/3b413470b0f990dc0d6e4287da02a6b6e21d3239/src/node/task-server.slow-spec.ts#L46 44 | 45 | const commandUnixNoop = 'true'; > 46 | const commandWindowsNoop = 'rundll32.exe'; 47 | 48 | /** Expects argv to be ['a', 'b', 'c'] */
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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
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.0
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-10-30, but eclipse-theia-bot 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.65.2
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-10-14, but eclipse-theia-bot 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.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.64.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.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 2025-06-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.62.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 (sgraband) than the most recent previously approved version (jfaltermeier) on 2025-06-12, 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.62.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.