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
152Mature · −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 bytes61,647
Previous version1.27.3
Published2026-06-09T10:26:30.500Z
SHA-2567d9a6d49accd0986e719b070d61194a35b327acb6713a657aab16e4cdafe9895

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.27.4Version
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

Scripts11
  • 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' '**/*.js'
  • setuprun --top-level browsers:setup
  • testrun test:it && run test:e2e && run test:coverage
  • test:coverageAPPLITOOLS_SHOW_LOGS=true APPLITOOLS_LOG_FILE="./logs/$(uuidgen).log" APPLITOOLS_SHOW_LOGS=true APPLITOOLS_LOG_FILE="./logs/$(uuidgen).log" APPLITOOLS_BATCH_NAME='JS Coverage Tests: eyes-nightwatch' APPLITOOLS_BATCH_ID=$(uuidgen) MOCHA_GROUP=coverage run --top-level mocha './test/generated-coverage/*.spec.js' --parallel --jobs ${MOCHA_JOBS:-15} --exit
  • test:e2enightwatch --config test/e2e/nightwatch.conf.js --eyes-config applitools.config.js test/e2e/*.spec.js
  • test:itMOCHA_GROUP=it run --top-level mocha './test/it/*.spec.ts'
  • test:localrun test:it && run test:e2e && MOCHA_OMIT_TAGS=sauce run test:coverage
  • test:sauceMOCHA_ONLY_TAGS=sauce run test:coverage
  • up:frameworkecho "$(jq '.devDependencies.nightwatch = $ENV.APPLITOOLS_FRAMEWORK_VERSION' ./package.json)" > ./package.json
Dependencies5
  • @applitools/driver1.26.2
  • @applitools/eyes1.43.1
  • @applitools/spec-driver-webdriver1.6.2
  • @applitools/utils1.14.5
  • webdriver7.31.1