@theia/remote
Theia - Remote
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 monorepo does not publish Sigstore provenance; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@theia/core | AI (dependencies): Sibling package in the eclipse-theia monorepo; always co-versioned and safe for this package. | ai | |
| phantom-deps | phantom-dep:socket.io | AI (phantom-deps): Declared runtime dep in package.json; used in backend remote module, not a true phantom. | ai | |
| phantom-deps | phantom-dep:express-http-proxy | AI (phantom-deps): Declared runtime dep in package.json; used in backend proxy logic, not a true phantom. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.72.2 | 18 / 7 | |
| 1.72.1 | 18 / 7 | |
| 1.72.0 | 18 / 7 | |
| 1.71.2 | 18 / 7 | |
| 1.70.2 | 18 / 7 | |
| 1.65.0 | 17 / 7 | |
| 1.64.1 | 17 / 7 | |
| 1.63.1 | 16 / 7 | |
| 1.62.2 | 16 / 7 | |
| 1.62.1 | 16 / 7 | |
| 1.62.0 | 16 / 7 |
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.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.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.
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.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.