← Home

@theia/ai-mcp-ui

Theia - MCP UI Integration

14
Versions
EPL-2.0 OR GPL-2.0-only WITH Classpath-exception-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

eclipsetheiavince-fugnittobhufmannmarc.dumaispaul-marechalmsujewtsmaederjfaltermeierjhelmingeclipse-theia-botsgrabandndoschek

Keywords

theia-extension

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Eclipse Theia monorepo migrated publishing to GitHub Actions with SLSA attestation; stable transition for this package. ai
license weak-copyleft-license:EPL-2.0 AI (license): EPL-2.0 is standard for Eclipse projects; stable for this package. ai
license copyleft-license:GPL-2.0-only AI (license): GPL-2.0 with Classpath exception is standard for Eclipse Theia; stable for this package. ai
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 monorepo dep at matching version; not an independent risk. ai
dependencies unvetted-dep:@theia/ai-core AI (dependencies): Sibling monorepo dep at matching version; not an independent risk. ai
dependencies unvetted-dep:@theia/ai-mcp AI (dependencies): Sibling monorepo dep at matching version; not an independent risk. ai

Versions (showing 14 of 14)

Version Deps Published
1.72.2 3 / 1
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.70.0 3 / 1
1.69.0 3 / 1
1.67.0 3 / 1
1.66.2 3 / 1
1.65.0 3 / 1
1.64.2 3 / 1
1.64.1 3 / 1

v1.72.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.72.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.72.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.71.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.70.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.70.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.69.0

1 finding
INFO Has SLSA provenance attestation provenance

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 findings
HIGH Publisher changed: eclipse-theia-bot → GitHub Actions (on 2025-12-10) provenance

This 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.

INFO Has SLSA provenance attestation provenance

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 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v1.65.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.64.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.64.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.