@theia/plugin-ext-vscode
Theia - Plugin Extension for VsCode
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/outline-view | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@theia/workspace | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@theia/filesystem | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@theia/plugin-ext | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@theia/userstorage | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@theia/callhierarchy | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@theia/typehierarchy | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@theia/scm | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@theia/editor | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@theia/monaco | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@theia/terminal | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@theia/navigator | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| provenance | publisher-changed | AI (provenance): Eclipse Theia migrated to GitHub Actions CI publishing with SLSA provenance; this is expected for the monorepo. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): ndoschek is a known Eclipse Theia contributor; addition is consistent with the project's maintainer roster. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @theia/scm is a first-party Theia package at matching version; no supply-chain risk. | ai | |
| dependencies | unvetted-dep:@theia/core | AI (dependencies): @theia/core is a sibling package in the Eclipse Theia monorepo; stable false positive for this package. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 1.72.3 | 18 / 1 | |
| 1.72.2 | 18 / 1 | |
| 1.72.1 | 18 / 1 | |
| 1.72.0 | 18 / 1 | |
| 1.71.2 | 18 / 1 | |
| 1.71.1 | 18 / 1 | |
| 1.71.0 | 18 / 1 | |
| 1.70.2 | 18 / 1 | |
| 1.70.1 | 18 / 1 | |
| 1.70.0 | 18 / 1 | |
| 1.69.0 | 18 / 1 | |
| 1.68.2 | 18 / 1 | |
| 1.68.1 | 18 / 1 | |
| 1.68.0 | 18 / 1 | |
| 1.67.0 | 18 / 1 | |
| 1.66.2 | 18 / 1 | |
| 1.66.1 | 18 / 1 | |
| 1.66.0 | 18 / 1 | |
| 1.65.2 | 18 / 1 | |
| 1.65.1 | 18 / 1 | |
| 1.65.0 | 18 / 1 | |
| 1.64.4 | 18 / 1 | |
| 1.64.3 | 18 / 1 | |
| 1.64.2 | 18 / 1 | |
| 1.64.1 | 18 / 1 | |
| 1.64.0 | 18 / 1 | |
| 1.63.3 | 17 / 1 | |
| 1.63.2 | 17 / 1 | |
| 1.63.1 | 17 / 1 | |
| 1.63.0 | 17 / 1 | |
| 1.62.2 | 17 / 1 | |
| 1.62.1 | 17 / 1 | |
| 1.62.0 | 17 / 1 | |
| 1.61.1 | 17 / 1 | |
| 1.61.0 | 17 / 1 |
v1.72.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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
2 findingsThis version was published by a different npm account than previous versions on 2026-05-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.72.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-28. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.71.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-27. This could indicate a legitimate maintainer transition or an account compromise.
Published 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.71.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.70.2
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
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 findingsThis version was published by a different npm account than previous versions on 2025-12-10. This could indicate a legitimate maintainer transition or an account compromise.
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.1
2 findingsThis version was published by a different npm account than previous versions on 2025-10-06. 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.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.4
2 findingsThis version was published by a different npm account than previous versions on 2025-10-10. 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.3
2 findingsThis version was published by a different npm account than previous versions on 2025-10-08. 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.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
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-07-01, 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.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.