@theia/ai-history
Theia - AI communication history
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Theia monorepo extension; link-heavy README and no-op common/index.js are standard patterns across all @theia/* packages. | ai | |
| dependencies | unvetted-dep:@theia/core | AI (dependencies): @theia/core is a core Theia framework dep; expected and stable across all @theia/* packages. | ai | |
| license | weak-copyleft-license:EPL-2.0 | AI (license): Standard Eclipse Public License used across all @theia/* packages. | ai | |
| license | copyleft-license:GPL-2.0-only | AI (license): Standard dual-license for Eclipse Theia; GPL-2.0 with Classpath exception is the documented alternative. | ai | |
| license | uncommon-license:Classpath-exception-2.0 | AI (license): Classpath exception is part of the standard Eclipse Theia dual-license; stable across all versions. | ai | |
| phantom-deps | phantom-dep:minimatch | AI (phantom-deps): minimatch is a declared runtime dependency in package.json; phantom-dep heuristic fires but it is legitimately used in the package. | ai | |
| phantom-deps | phantom-dep:@theia/workspace | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@theia/output | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@theia/filesystem | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.72.2 | 7 / 1 | |
| 1.72.1 | 7 / 1 | |
| 1.72.0 | 7 / 1 | |
| 1.71.2 | 7 / 1 | |
| 1.70.2 | 7 / 1 | |
| 1.70.1 | 7 / 1 | |
| 1.70.0 | 7 / 1 | |
| 1.69.0 | 7 / 1 | |
| 1.68.1 | 7 / 1 | |
| 1.67.0 | 7 / 1 | |
| 1.66.0 | 7 / 1 | |
| 1.64.2 | 8 / 1 | |
| 1.64.1 | 8 / 1 | |
| 1.64.0 | 8 / 1 | |
| 1.63.3 | 8 / 1 | |
| 1.63.0 | 8 / 1 | |
| 1.62.0 | 8 / 1 | |
| 1.61.1 | 7 / 1 | |
| 1.61.0 | 7 / 1 |
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.70.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.70.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.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.67.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.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.64.2
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.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.0
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.
v1.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.