@composio/client 2.1.36
PkgFire would install this release with a warning.·Checked 59 minutes ago·Published 19 November 2026
Why
-
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.1.36warn19 Nov 20262.1.35warn18 Nov 20262.1.34warn18 Nov 20262.1.33warn16 Nov 20262.1.32warn13 Nov 20262.1.31allow12 Nov 20262.1.30allow12 Nov 20262.1.29allow12 Nov 20262.1.28allow12 Nov 20262.1.27allow11 Nov 20262.1.26allow11 Nov 20262.1.25allow11 Nov 20262.1.24allow11 Nov 20262.1.23allow11 Nov 20262.1.22allow11 Nov 20262.1.21allow11 Nov 20262.1.20allow11 Nov 20262.1.19allow11 Nov 20262.1.18allow11 Nov 20262.1.17allow11 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.