This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 5.1.1 instead.
Reason given by maintainers: Partial release: requires fux-core==4.1.1, which was never published. Use 5.0.0.
fux-decoder-pdf
Part of fux — rank your written knowledge from a small index committed to git; fetch content from the systems that own it; verify freshness at answer time.
fux-decoder-pdf is a fux decoder package: PDF. Only fux-engine is mandatory;
everything else is declared per repository in the committed
.fux/plugins.toml, pinned to one version and digest, and refused loudly when
it is missing or differs, so two machines on one repository never build
different indexes.
It reads .pdf. Install it and declare it in .fux/plugins.toml --
fux setup proposes it when your sources hold those files -- or fux does not
read them, and fux doctor says so.
It is released on fux's own version, together with every other fux package. Documentation: https://github.com/arpitarya/fux#readme
1 maintainer
Metadata
1 maintainer
Release files for fux-decoder-pdf 4.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fux_decoder_pdf-4.1.1-py3-none-any.whl | Python 3 | none | any | Details for fux_decoder_pdf-4.1.1-py3-none-any.whl |
Release files / fux_decoder_pdf-4.1.1-py3-none-any.whl
| Download URL | fux_decoder_pdf-4.1.1-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0b4c78a749e52d2fbb553440f11012b3be1b0edcbdd5dbdd862ea95fd3f46de5
|
|
BLAKE2b-256 checksum How to use checksums |
0810dc0d55cc059983356f3258160a77e93ca61bb952a52f559471181d4cc3cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Security for fux-decoder-pdf 4.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
