djlint 1.50.0
PkgFire would install this release with a warning.·Checked 15 minutes ago·Published 11 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
- Not signed
- Build provenance
- Attested
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
1.50.0warn11 Nov 20261.49.10warn7 Nov 20261.49.9allow3 Nov 20261.49.8allow3 Nov 20261.49.7allow3 Nov 20261.49.6allow3 Nov 20261.49.5allow3 Nov 20261.49.4allow3 Nov 20261.49.3allow2 Nov 20261.49.2allow1 Nov 20261.49.1allow1 Nov 20261.49.0warn1 Nov 20261.48.1allow31 Oct 20261.48.0allow31 Oct 20261.47.1allow26 Oct 20261.47.0allow22 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.