← Home

@theia/ai-chat

Theia - AI Chat Extension

13
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
phantom-deps phantom-dep:minimatch AI (phantom-deps): minimatch is a declared runtime dependency in package.json; phantom-dep heuristic false positive for this package. ai
dependencies unvetted-dep:@theia/editor AI (dependencies): Sibling monorepo package; always released together at matching versions. ai
dependencies unvetted-dep:@theia/monaco AI (dependencies): Sibling monorepo package; always released together at matching versions. ai
dependencies unvetted-dep:@theia/ai-core AI (dependencies): Sibling monorepo package; always released together at matching versions. ai
dependencies unvetted-dep:@theia/core AI (dependencies): Sibling monorepo package; always released together at matching versions. ai
dependencies unvetted-dep:@theia/filesystem AI (dependencies): Sibling monorepo package; always released together at matching versions. ai
dependencies unvetted-dep:@theia/file-search AI (dependencies): Sibling monorepo package; always released together at matching versions. ai
dependencies unvetted-dep:@theia/workspace AI (dependencies): Sibling monorepo package; always released together at matching versions. ai
phantom-deps phantom-dep:js-yaml AI (phantom-deps): js-yaml is a declared runtime dependency in package.json; phantom-dep heuristic misfires for this package. ai

Versions (showing 13 of 13)

Version Deps Published
1.72.2 10 / 1
1.72.1 10 / 1
1.72.0 10 / 1
1.71.2 10 / 1
1.71.0 10 / 1
1.70.2 10 / 1
1.69.0 10 / 1
1.68.0 10 / 1
1.65.0 10 / 1
1.64.4 11 / 1
1.64.0 11 / 1
1.63.3 11 / 1
1.63.1 11 / 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.71.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.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.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.4

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

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