@theia/property-view
Theia - Property View 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): Theia is an established Eclipse project; lack of provenance is common and not a risk signal here. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): ndoschek is a known Theia project contributor; addition consistent with legitimate project maintainer expansion. | ai | |
| provenance | publisher-changed | AI (provenance): ndoschek is a verified eclipse-theia org maintainer with 221 approved packages; publisher rotation within the org is expected. | ai | |
| dependencies | unvetted-dep:@theia/core | AI (dependencies): Sibling monorepo dependency released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@theia/filesystem | AI (dependencies): Sibling monorepo dependency released in lockstep; not an independent risk. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.72.1 | 3 / 1 | |
| 1.72.0 | 3 / 1 | |
| 1.71.2 | 3 / 1 | |
| 1.71.0 | 3 / 1 | |
| 1.70.2 | 3 / 1 | |
| 1.70.1 | 3 / 1 | |
| 1.68.1 | 3 / 1 | |
| 1.68.0 | 3 / 1 | |
| 1.67.0 | 3 / 1 | |
| 1.64.4 | 3 / 1 | |
| 1.64.2 | 3 / 1 | |
| 1.64.1 | 3 / 1 | |
| 1.63.1 | 3 / 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.68.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. 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.68.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-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.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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.