npm PACKAGE

trigger.dev 4.8.0

Warn

PkgFire would install this release with a warning.·Checked 1 hour ago·Published 23 October 2026

Why

warnSuspicious behaviour

Detects suspicious autostart persistence mechanisms
warnSuspicious behaviour

Detects destructive operations (recursive deletion, wiping)
warnSuspicious behaviour

Detects access to sensitive files (credentials, configs, keys)
warnSuspicious behaviour

Possible credential in the published package: generic-api-key

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.

Code reading

PkgFire's own reading of the files: what the code can do.

code-execdist/esm/dev/devSupervisor.js, dist/esm/executions/taskRunProcess.js, dist/esm/indexing/indexWorkerManifest.js, dist/esm/utilities/linux.js
code-networkdist/esm/apiClient.js, dist/esm/commands/deploy.js, dist/esm/dev/devWatchdog.js, dist/esm/entryPoints/managed/overrides.js, dist/esm/mcp/mintlifyClient.js

Source patterns

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

capability-filesystem-delete
capability-filesystem-read
capability-network-download
capability-network-outbound
capability-process-spawn
threat-filesystem-autostart
threat-filesystem-destruction
threat-filesystem-read
threat-process-spawn-silent
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.

Start free How it works