@theia/application-package
Theia application package API.
Supply chain provenance
Status for the latest visible version.
Maintainers
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): Monorepo sub-package; sparse README and no keywords are normal for Eclipse Theia workspace packages. | ai | |
| phantom-deps | phantom-dep:@types/semver | AI (phantom-deps): @types/* packages are type-only and not directly imported; stable false positive for TypeScript packages. | ai | |
| phantom-deps | phantom-dep:@types/fs-extra | AI (phantom-deps): @types/* packages are type-only and not directly imported; stable false positive for TypeScript packages. | ai | |
| phantom-deps | phantom-dep:@types/write-json-file | AI (phantom-deps): @types/* packages are type-only and not directly imported; stable false positive for TypeScript packages. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 1.72.2 | 12 / 1 | |
| 1.72.1 | 12 / 1 | |
| 1.72.0 | 12 / 1 | |
| 1.71.2 | 12 / 1 | |
| 1.71.1 | 12 / 1 | |
| 1.70.2 | 12 / 1 | |
| 1.70.1 | 12 / 1 | |
| 1.70.0 | 12 / 1 | |
| 1.69.0 | 12 / 1 | |
| 1.68.2 | 12 / 1 | |
| 1.68.1 | 12 / 1 | |
| 1.68.0 | 12 / 1 | |
| 1.67.0 | 12 / 1 | |
| 1.66.2 | 12 / 1 | |
| 1.66.1 | 12 / 1 | |
| 1.66.0 | 12 / 1 | |
| 1.65.2 | 12 / 1 | |
| 1.65.1 | 12 / 1 | |
| 1.65.0 | 12 / 1 | |
| 1.64.4 | 12 / 1 | |
| 1.64.3 | 12 / 1 | |
| 1.64.2 | 12 / 1 | |
| 1.64.1 | 12 / 1 | |
| 1.64.0 | 12 / 1 | |
| 1.63.3 | 12 / 1 | |
| 1.63.2 | 12 / 1 | |
| 1.63.1 | 12 / 1 | |
| 1.63.0 | 12 / 1 | |
| 1.62.2 | 12 / 1 | |
| 1.62.1 | 12 / 1 | |
| 1.62.0 | 12 / 1 | |
| 1.61.1 | 12 / 1 | |
| 1.61.0 | 12 / 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.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.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.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.1
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.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.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.1
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
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.1
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.1
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.