ty 0.0.104
PkgFire would install this release with a warning.·Checked 41 minutes ago·Published 13 November 2026
Why
-
warnSuspicious behaviour
Detects unicode homoglyphs and uncommon characters used for obfuscation
-
warnSuspicious behaviour
Binary file/s detected in package: 572cd07f51799ac97b9965fbf65b74d6ed96c5c27a06bf2856dc6d4404e7edc8: ty (elf)
-
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
- 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
0.0.104warn13 Nov 20260.0.103warn13 Nov 20260.0.102warn12 Nov 20260.0.101warn11 Nov 20260.0.100warn9 Nov 20260.0.99warn6 Nov 20260.0.98warn5 Nov 20260.0.97warn4 Nov 20260.0.96warn3 Nov 20260.0.95warn29 Oct 20260.0.94warn28 Oct 20260.0.93warn28 Oct 20260.0.92warn26 Oct 20260.0.91warn22 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.