@splinetool/runtime 2.0.117
PkgFire would install this release with a warning.·Checked 34 hours ago·Published 28 October 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 2 days 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.126warn30 Oct 20262.0.125warn30 Oct 20262.0.124warn30 Oct 20262.0.122warn30 Oct 20262.0.121warn29 Oct 20262.0.120warn29 Oct 20262.0.119warn29 Oct 20262.0.118warn28 Oct 20262.0.117warn28 Oct 20262.0.116warn28 Oct 20262.0.115warn28 Oct 20262.0.114warn27 Oct 20262.0.113warn26 Oct 20262.0.112warn26 Oct 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.