@redocly/cli 2.79.0
PkgFire would install this release with a warning.·Checked 6 hours ago·Published 16 November 2026
Why
-
warnSuspicious behaviour
Detects access to sensitive files (credentials, configs, keys)
-
warnSuspicious behaviour
Detects advanced API call obfuscation using introspection and reflection techniques
-
warnSuspicious behaviour
Detects base64 decoding followed by code execution
-
warnSuspicious behaviour
Detects unicode homoglyphs and uncommon characters used for obfuscation
-
warnRelease cooldown
Published 5 hours 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
- 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.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
2.79.0warn16 Nov 20262.78.0warn12 Nov 20262.77.0warn9 Nov 20262.76.0warn5 Nov 20261.34.24warn5 Nov 20262.75.0warn4 Nov 20262.74.0warn4 Nov 20262.73.0warn3 Nov 20261.34.23warn2 Nov 20262.72.1warn29 Oct 20262.72.0warn28 Oct 20262.71.2warn27 Oct 20262.71.1warn26 Oct 20262.71.0warn23 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.