PkgRadar

Package evidence

[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
110Mature · −50% score
First published
Dec 2016
Publisher
infinitered-owner

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":["[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":["[email protected]"],"fail_on":"review"}'
Publisherinfinitered-owner
Artifact bytes99,243
Previous version5.2.1
Published2025-11-24T19:02:22.991Z
SHA-2564a1e2e7acd4c8450225190d033879708d8e174509b98d1f118962c63fda8b891

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

Scripts17
  • buildyarn format && yarn clean-build && yarn compile && yarn copy-templates && yarn create-direct && yarn clean-types && echo 'Run yarn clean-build to remove build artifacts.'
  • ci:publishyarn build && yarn semantic-release
  • ci:testyarn lint && yarn test --maxWorkers=2 && yarn integration
  • clean-buildrimraf ./build && node ./.circleci/removeDirect.js
  • clean-typesnode .circleci/cleanDir.js ./build/types
  • compiletsc -p .
  • copy-templatescp -a ./src/cli/templates ./build/cli/
  • create-directnode ./.circleci/createDirect.js
  • formatprettier --write "{**/*.ts,**/*.js,.circleci/**/*.js}" --loglevel error && eslint . --fix
  • integrationyarn build && jest --config=./.circleci/jest-integration.config.json
  • linteslint .
  • preparehusky install
  • semantic-releasesemantic-release
  • snapupdatejest --updateSnapshot
  • testjest
  • watchjest --watch
  • windows:testyarn && yarn format && yarn test && yarn clean-build && yarn compile && yarn copy-templates && jest --config=./.circleci/jest-integration.config.json
Dependencies16
  • apisauce^3.1.0
  • app-module-path^2.2.0
  • cli-table30.6.0
  • colors1.4.0
  • cosmiconfig7.0.1
  • cross-spawn7.0.6
  • ejs3.1.10
  • enquirer2.3.6
  • execa5.1.1
  • fs-jetpack4.3.1
  • lodash^4.17.21
  • ora4.0.2
  • pluralize^8.0.0
  • semver7.7.0
  • which2.0.2
  • yargs-parser^21.0.0