Proffer is fast and flexible tool for protein inference in bottom-up proteomics experiments.
Installation
This library requires Python 3.10+ and can be installed with pip:
pip install proffer
Basic Usage
After installation, you can run the proffer CLI tool:
proffer data/percolator.txt --format tsv
You can also load results directly from any URI supported by fsspec:
# HTTP(S)
proffer https://github.com/seerbio/proffer/raw/refs/heads/main/data/percolator.txt --format tsv
# S3
pip install proffer[s3] # ensure libraries for S3 support are installed
proffer s3://bucket/key/results.parquet --format parquet
Basic support is included for thresholding peptide identifications before inference:
proffer data/percolator.txt --format tsv --qvalue-threshold 0.01
By default output is written in JSON format to stdout.
Alternatively, the -o flag can be used to write results to Parquet:
proffer data/percolator.txt --output proffer-results.parquet
It is possible to configure the column names used, as well as the approach used to pick protein groups. To learn more about the available options you can run:
proffer --help
Python usage
To use Proffer in your Python code, call proffer.infer with a Polars DataFrame:
import proffer
result_frame = proffer.infer(polars_frame)
It is possible to configure the column names used, as well as the approach used to pick protein groups. To learn more about the available options you can run:
help(proffer.infer)
Usage with Fulcrum Pipeline
Utilities for working with Spark-based datasets can be found in proffer.spark.
These use interfaces from wheely-mammoth
(compatible with Fulcrum Pipeline™) to efficiently read peptide and protein
information and compute inference.
For typical use cases, it will be easiest to employ a pre-built Fulcrum workflow that uses Proffer for inference, rather than call these utilities directly.
By default, installing Proffer will not install Spark dependencies; to use Proffer in an environment where these are not already installed, run:
pip install 'proffer[spark]'
Metadata
Release files for proffer 0.5.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| proffer-0.5.3.tar.gz | 5.5 MB | With provenance | Details for proffer-0.5.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| proffer-0.5.3-py3-none-any.whl | Python 3 | none | any | Details for proffer-0.5.3-py3-none-any.whl |
Total release size: 5.5 MB
Release files / proffer-0.5.3.tar.gz
| Download URL | proffer-0.5.3.tar.gz |
|---|---|
| Size | 5.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7a32eb254974085117eb8e06a704e9266f588597e8b3f26ad238218799fd9bfe
|
|
BLAKE2b-256 checksum How to use checksums |
1d4eaca9c4a2870a2bb951ff16642006ce43e9587a0fb5fbd47fe4fe05abce02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 1, 2026.
Transparency logRelease files / proffer-0.5.3-py3-none-any.whl
| Download URL | proffer-0.5.3-py3-none-any.whl |
|---|---|
| Size | 42.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9c48f118c9981645eeee46097ec15e37b3fa98f8213c4510cfad924a88c80ab0
|
|
BLAKE2b-256 checksum How to use checksums |
c09f3e3f9401aca2563c8da5f7d7e3bb6f91850b958eeca14227a0e6648ef5c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 1, 2026.
Transparency logSecurity for proffer 0.5.3
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for proffer-0.5.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 1, 2026.
Transparency logA 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.