opik 2.2.132
PkgFire would install this release with a warning.·Checked 16 hours ago·Published 29 October 2026
Why
-
warnSuspicious behaviour
Detects download-and-execute patterns: fetching a remote file then executing it
-
warnSuspicious behaviour
Detects heavy code obfuscation techniques
-
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
- Not signed
- 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.2.137warn30 Oct 20262.2.136warn30 Oct 20262.2.135warn30 Oct 20262.2.134warn30 Oct 20262.2.133warn29 Oct 20262.2.132warn29 Oct 20262.2.131warn28 Oct 20262.2.130warn28 Oct 20262.2.129warn28 Oct 20262.2.128warn28 Oct 20262.2.127warn27 Oct 20262.2.126warn27 Oct 20262.2.125warn27 Oct 20262.2.124warn27 Oct 20262.2.123warn27 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.