npm PACKAGE

autoevals 0.3.0

Warn

PkgFire would install this release with a warning.·Checked 6 days ago·Published 9 June 2026

npmjs.com

Why

  • warnInstall script added

    The preinstall script is new or changed since 0.0.132: preinstall "node -e \"const userAgent = process.env.npm_config_user_agent || ''; if (process.env.INIT_CWD === process.cwd() && !us...". A release that starts running code on install is how event-stream, ua-parser-js and the 2025 npm worms spread. It was already installed before this scan.

Provenance

A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.

Signature
Verified against the registry's key
Build provenance
Attested · source commit ↗

What the code does

On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.

Source patterns

Patterns found in the source, including those malware is known to use.

  • capability-process-hooks
  • threat-npm-preinstall-script
  • threat-process-hooks
  • threat-runtime-environment-read

Other checked releases

Check every dependency before it installs

This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.