PkgRadar

Package evidence

@applitools/[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
160Mature · −50% score
First published
Nov 2020
Publisher
movsho

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":["@applitools/[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":["@applitools/[email protected]"],"fail_on":"review"}'
Publishermovsho
Artifact bytes59,558
Previous version1.31.22
Published2026-06-09T10:26:37.367Z
SHA-256d59500f93e06e869b6a4584cb0a0f8de4dad5d2054dd88aa1e8deb5384fb5a9f

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
1.31.23Version
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

Scripts9
  • buildrun --top-level tspc --project ./tsconfig.build.json
  • generate:testsNODE_OPTIONS='--experimental-import-meta-resolve --experimental-loader=@applitools/generic/dist/code-loader.js' generic ./test/generic/config.mjs
  • lintrun --top-level eslint '**/*.ts'
  • puppeteer:setupPUPPETEER_PRODUCT=firefox node --eval 'import("puppeteer/install.mjs").catch(() => import("puppeteer/install.js"))'
  • puppeteer:setup-chrome-onlypuppeteer browsers install chrome
  • setup[[ "$APPLITOOLS_FRAMEWORK_VERSION" != "21" ]] && yarn puppeteer:setup || yarn puppeteer:setup-chrome-only
  • testyarn test:coverage
  • test:coverageAPPLITOOLS_SHOW_LOGS=true APPLITOOLS_LOG_FILE="./logs/$(uuidgen).log" APPLITOOLS_BATCH_NAME='JS Coverage Tests: eyes-puppeteer' APPLITOOLS_BATCH_ID=$(uuidgen) MOCHA_GROUP=coverage run --top-level mocha './test/generated-coverage/*.spec.js' --parallel --jobs ${MOCHA_JOBS:-15} --exit
  • up:frameworkecho "$(jq '.devDependencies.puppeteer = $ENV.APPLITOOLS_FRAMEWORK_VERSION' ./package.json)" > ./package.json
Dependencies2
  • @applitools/eyes1.43.1
  • @applitools/spec-driver-puppeteer1.8.2