@splinetool/runtime 2.0.165
PkgFire would install this release with a warning.·Checked 52 minutes ago·Published 10 November 2026
Why
-
warnSuspicious behaviour
Detects destructive operations (recursive deletion, wiping)
-
warnSuspicious behaviour
Detects download-and-execute patterns: fetching a remote file then executing it
-
warnSuspicious behaviour
Detects base64 decoding followed by code execution
-
warnSuspicious behaviour
Detects steganography decode followed by code execution
-
warnRelease cooldown
Published less than an hour ago, inside the 7-day cooldown. Most malicious releases are pulled within hours of publication, so a version this new has not yet had time to be caught.
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
- None, and no earlier version had any
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.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
2.0.169warn10 Nov 20262.0.168warn10 Nov 20262.0.167warn10 Nov 20262.0.166warn10 Nov 20262.0.165warn10 Nov 20262.0.164warn10 Nov 20262.0.163warn10 Nov 20262.0.162warn10 Nov 20262.0.161warn10 Nov 20262.0.160warn10 Nov 20262.0.159warn9 Nov 20262.0.158warn9 Nov 20262.0.157warn9 Nov 20262.0.156warn9 Nov 20262.0.155warn9 Nov 20262.0.154warn9 Nov 20262.0.153warn9 Nov 20262.0.152warn9 Nov 20262.0.149warn6 Nov 20262.0.148warn6 Nov 2026
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.