@openclaw/ai 2026.10.33
PkgFire would install this release with a warning.·Checked 30 minutes ago·Published 18 November 2026
Why
-
warnSuspicious behaviour
1 new behaviour since 2026.10.10
-
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
- 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
2026.10.33warn18 Nov 20262026.11.5warn17 Nov 20262026.11.4warn16 Nov 20262026.9.37allow10 Nov 20262026.11.3warn10 Nov 20262026.11.2allow8 Nov 20262026.11.1allow5 Nov 20262026.10.10allow3 Nov 20262026.9.36allow29 Oct 20262026.10.9allow29 Oct 20262026.10.8allow27 Oct 20262026.9.35allow27 Oct 20262026.9.34allow24 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.