@theia/ai-core-ui
Theia - AI Core UI
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 | publisher-changed | AI (provenance): Trusted maintainer rotation within eclipse-theia org, no behavior change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consistent with normal Theia monorepo maintainer rotation. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known implicit runtime dep for TypeScript packages; stable false positive for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.73.1 | 3 / 1 | |
| 1.73.0 | 3 / 1 | |
| 1.72.3 | 3 / 1 | |
| 1.72.2 | 3 / 1 | |
| 1.72.1 | 3 / 1 | |
| 1.72.0 | 3 / 1 | |
| 1.71.2 | 3 / 1 | |
| 1.71.1 | 3 / 1 | |
| 1.71.0 | 3 / 1 | |
| 1.70.2 | 3 / 1 | |
| 1.70.1 | 3 / 1 | |
| 1.70.0 | 3 / 1 | |
| 1.69.0 | 3 / 1 | |
| 1.68.2 | 3 / 1 | |
| 1.68.1 | 3 / 1 | |
| 1.68.0 | 3 / 1 | |
| 1.67.0 | 3 / 1 | |
| 1.66.2 | 3 / 1 | |
| 1.66.1 | 3 / 1 | |
| 1.66.0 | 3 / 1 | |
| 1.65.2 | 3 / 1 | |
| 1.65.1 | 3 / 1 | |
| 1.65.0 | 3 / 1 | |
| 1.64.4 | 3 / 1 | |
| 1.64.3 | 3 / 1 | |
| 1.64.2 | 3 / 1 | |
| 1.64.1 | 3 / 1 | |
| 1.64.0 | 3 / 1 |
v1.73.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.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.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.0
1 findingPublished 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.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
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 it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. 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.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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.