← Home

@theia/plugin-ext

Theia - Plugin Extension

19
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
semgrep semgrep:new-function-constructor AI (semgrep): Used exclusively for dynamic ESM import() interop in CJS context — standard pattern, not arbitrary code execution. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get used for API proxy/binding pattern in plugin context — standard for VS Code-compatible plugin APIs. ai
phantom-deps phantom-dep:@types/mime AI (phantom-deps): Type-only package; not directly imported at runtime by convention. ai
semgrep semgrep:child-process-import AI (semgrep): Plugin host process spawning is core functionality of a plugin extension host; expected and documented. ai
phantom-deps phantom-dep:@theia/bulk-edit AI (phantom-deps): Same-org monorepo dep; loaded via Theia DI framework, not direct import. ai
phantom-deps phantom-dep:@theia/preferences AI (phantom-deps): Same-org monorepo dep; loaded via Theia DI framework, not direct import. ai
phantom-deps phantom-dep:@theia/messages AI (phantom-deps): Same-org monorepo dep; loaded via Theia DI framework, not direct import. ai

Versions (showing 19 of 19)

Version Deps Published
1.73.1 46 / 4
1.73.0 46 / 4
1.72.3 45 / 4
1.72.2 45 / 4
1.72.1 45 / 4
1.72.0 45 / 4
1.71.2 45 / 4
1.71.1 45 / 4
1.71.0 45 / 4
1.70.2 45 / 4
1.70.1 45 / 4
1.70.0 45 / 4
1.69.0 45 / 4
1.68.2 45 / 4
1.68.1 45 / 4
1.68.0 45 / 4
1.67.0 45 / 4
1.66.2 45 / 4
1.66.1 45 / 4

v1.73.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.68.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.68.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.68.0

2 findings
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.

INFO Publisher changed: eclipse-theia-bot → GitHub Actions (on 2026-01-29, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (eclipse-theia-bot) on 2026-01-29, 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.67.0

2 findings
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.

INFO Publisher changed: eclipse-theia-bot → GitHub Actions (on 2025-12-10, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (eclipse-theia-bot) on 2025-12-10, 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.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.66.1

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.