sqltrie 0.11.3
PkgFire would install this release with a warning.·Checked 16 hours ago·Published 1 September 2026
Why
-
warnPublisher changed
Uploaded through the trusted publisher GitHub treeverse/sqltrie · release.yml, but 0.11.2 was uploaded through GitHub iterative/sqltrie · release.yml. Registering a trusted publisher on PyPI needs the project's account rather than its repository, so releases that start coming from another repository are what a taken-over account looks like. A project that moved or renamed its repository produces the same change - check which this is.
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.
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.