@eclipse-che/api
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped Eclipse Che package; Levenshtein match to 'hapi' is a false positive for this namespace. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped Eclipse Che package; Levenshtein match to 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped Eclipse Che package; Levenshtein match to 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped Eclipse Che package; Levenshtein match to 'ajv' is a false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Type-definition-only package (ships index.d.ts); no deps, no code blocks, no repo URL are expected for this package type. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 7.118.0 | 0 / 0 | |
| 7.117.0 | 0 / 0 | |
| 7.113.0 | 0 / 0 | |
| 7.112.0 | 0 / 0 | |
| 7.111.0 | 0 / 0 | |
| 7.110.0 | 0 / 0 | |
| 7.109.0 | 0 / 0 | |
| 7.108.0 | 0 / 0 | |
| 7.107.0 | 0 / 0 | |
| 7.106.0 | 0 / 0 | |
| 7.105.0 | 0 / 0 | |
| 7.104.0 | 0 / 0 |
v7.118.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.117.0
2 findingsPackage name '@eclipse-che/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.113.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mkuznets) than the most recent previously approved version (eclipse_che) on 2025-12-19, but mkuznets is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.112.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.111.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.110.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.109.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.108.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.107.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.106.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.105.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.104.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.