PkgRadar

Package evidence

@eclipse-che/[email protected]

no findings

Trust signals

Why this verdict

PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.

Versions published
499Mature · −50% score
First published
Nov 2021
Publisher
mkuznets

Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd to CI gate
Block this release in CIcurl · GitHub Actions

Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.

curl -fsS https://pkgradar.com/gate/npm \
  -H "Authorization: Bearer $PKGRADAR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"specs":["@eclipse-che/[email protected]"],"fail_on":"review"}'

GitHub Actions step:

- name: PkgRadar gate
  run: |
    curl -fsS https://pkgradar.com/gate/npm \
      -H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
      -H "Content-Type: application/json" \
      -d '{"specs":["@eclipse-che/[email protected]"],"fail_on":"review"}'
Publishermkuznets
Artifact bytes316,017
Previous version7.118.0
Published2026-05-21T11:47:12.472Z
SHA-25620829f9f83bf6bc3a8b75a2c245c7e954aba1bc73d379de3e88b0ae2c4abcadb

Why flagged

What the scanner saw

No high-signal static finding in the saved report.

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

low
Last checked
lowRisk
0Score
7.119.0-next-39dbec7Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts13
  • cleanup-dockerif [ $(docker ps -a | grep -c selenium-e2e) -gt 0 ]; then docker rm -f $(docker ps --filter "name=selenium-e2e" -aq); fi;
  • delayed-testnpm run lint && npm run tsc && export TS_USE_WEB_DRIVER_FOR_TEST=false && export MOCHA_DELAYED_SUITE=true && mocha --config dist/configs/mocharc.js --delay
  • devfile-acceptance-test-suiteconfigs/sh-scripts/runDevfileAcceptanceTests.sh
  • driver-less-testexport TS_USE_WEB_DRIVER_FOR_TEST=false && npm run test
  • functional-test-suiteconfigs/sh-scripts/runFunctionalTests.sh
  • linteslint --fix .
  • open-allure-dasboardallure generate .allure-results --clean -o .allure-report && allure open .allure-report
  • prettierprettier --config .prettierrc.json . --write
  • test./configs/sh-scripts/initDefaultValues.sh npm run lint && npm run tsc && export USERSTORY=$USERSTORY && mocha --config dist/configs/mocharc.js
  • test-all-devfiles ./configs/sh-scripts/initDefaultValues.sh && ./configs/sh-scripts/initDevfileTests.sh
  • test-dockernpm run cleanup-docker && docker run -it --shm-size=2g -p 5920:5920 --name selenium-e2e -e TS_SELENIUM_BASE_URL=$TS_SELENIUM_BASE_URL eclipse/che-e2e:nightly
  • test-docker-mount-e2enpm run cleanup-docker && docker run -it --shm-size=2g -p 5920:5920 --name selenium-e2e -e TS_SELENIUM_BASE_URL=$TS_SELENIUM_BASE_URL -v $(pwd):/tmp/e2e:Z eclipse/che-e2e:nightly
  • tscrm -rf ./dist && ./configs/sh-scripts/generateIndex.sh && tsc -p .
Dependencies3
  • @eclipse-che/apilatest
  • inversify6.0.1
  • reflect-metadata0.1.13