@eclipse-che/che-devworkspace-generator
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@devfile/api | AI (dependencies): @devfile/api is the upstream devfile API package from the same org; pre-release version stamp is expected for CI builds. | ai | |
| npm-metadata | url-dep:license-tool | AI (npm-metadata): SHA-pinned devDependency used only for license-check scripts; not included in published package files. | ai | |
| phantom-deps | phantom-dep:jsonc-parser | AI (phantom-deps): jsonc-parser is declared in dependencies and used in the package; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 7.117.0 | 8 / 12 | |
| 7.116.0 | 8 / 12 | |
| 7.115.0 | 8 / 11 | |
| 7.114.0 | 8 / 11 | |
| 7.104.0 | 9 / 9 |
v7.117.0
2 findingsDependency 'license-tool' in `devDependencies` points to 'git+https://github.com/che-incubator/dash-licenses.git#c09f697ea6336ce82d365654dfeb7ef6e9c84768' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.116.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.115.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.114.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.104.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.