@theia/getting-started
Theia - GettingStarted 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Eclipse Theia does not publish with Sigstore provenance; stable across all versions. | ai | |
| dependencies | unvetted-dep:@theia/editor | AI (dependencies): Sibling monorepo package from eclipse-theia/theia; unvetted status is a pipeline artifact. | ai | |
| dependencies | unvetted-dep:@theia/keymaps | AI (dependencies): Sibling monorepo package from eclipse-theia/theia; unvetted status is a pipeline artifact. | ai | |
| dependencies | unvetted-dep:@theia/core | AI (dependencies): Sibling monorepo package from eclipse-theia/theia; unvetted status is a pipeline artifact, not a real risk. | ai | |
| dependencies | unvetted-dep:@theia/workspace | AI (dependencies): Sibling monorepo package from eclipse-theia/theia; unvetted status is a pipeline artifact. | ai | |
| dependencies | unvetted-dep:@theia/filesystem | AI (dependencies): Sibling monorepo package from eclipse-theia/theia; unvetted status is a pipeline artifact. | ai | |
| dependencies | unvetted-dep:@theia/preview | AI (dependencies): Sibling monorepo package from eclipse-theia/theia; unvetted status is a pipeline artifact. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.72.2 | 7 / 1 | |
| 1.72.1 | 7 / 1 | |
| 1.72.0 | 7 / 1 | |
| 1.71.2 | 7 / 1 | |
| 1.70.2 | 7 / 1 | |
| 1.70.0 | 7 / 1 | |
| 1.68.2 | 7 / 1 | |
| 1.67.0 | 7 / 1 | |
| 1.65.0 | 7 / 1 | |
| 1.64.2 | 7 / 1 | |
| 1.63.0 | 7 / 1 | |
| 1.62.2 | 7 / 1 | |
| 1.62.0 | 7 / 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.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.67.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.2
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.