Practical, portable, performant digital signal processing.
doppler is a C99 DSP library — NCO, FIR, FFT, polyphase resampling, DDC,
AGC, carrier and burst acquisition, DSSS receivers, convolutional and
Reed-Solomon coding, CCSDS framing and more — with file, buffer, and
NATS-based streaming, and a
scenario-driven waveform generator (wfmgen) with byte-identical
CLI/Python/C parity. Python and Rust wrap the same C core — no second
implementation, no divergence, full SIMD throughput from any language.
New here? Start with Start Here — a one-page map from "what are you trying to do" to the right doc.
Navigate — Quick Start · Architecture · Gallery · Examples · Guides · Waveform Generator · Design · Contributing
API Reference — Full Python + C API index
Why it's built this way
Every algorithm lives in C exactly once. The Python layer is type conversion and lifetime bridging — a few hundred lines of glue, not a reimplementation. Bugs get fixed once, benchmarks reflect real hardware, and a C transmitter talks to a Python subscriber without surprises.
Performance
Measured throughput, per build and per machine, is on
Benchmarks — generated by make bench-docs rather than
quoted here, so it cannot go stale. make bench measures your hardware.
Try it
pip install doppler-dsp
from doppler.spectral import FFT
import numpy as np
x = np.random.randn(1024).astype(np.complex64)
X = FFT(1024).execute_cf32(x)
print(f"FFT: {len(x)} samples in -> {X.shape[0]} complex64 bins out")
Everything else — install options, the waveform generator, streaming, building from source — is in Quick Start.
Docs
Full docs: doppler-dsp.github.io/doppler
Licensing
MIT. The core C library is pure C99 and links -lm and -lpthread. Its FFT
uses the
vendored pocketfft (BSD-3-Clause) for double precision and arbitrary sizes, and
the vendored PFFFT (Pommier/FFTPACK, BSD) for the native single-precision SIMD
path. The optional NATS stream component (libdoppler_stream) vendors
nats.c (Apache-2.0) — it too is pure C99, so no C++ toolchain is needed
anywhere in the build.
1 maintainer
Metadata
1 maintainer
Release files for doppler-dsp 0.59.0
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 | |
|---|---|---|---|---|
| doppler_dsp-0.59.0.tar.gz | 25.9 MB | With provenance | Details |
Built distributions (wheels)
Total release size: 209.9 MB
Release files / doppler_dsp-0.59.0.tar.gz
| Download URL | doppler_dsp-0.59.0.tar.gz |
|---|---|
| Size | 25.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aeec56d9ebb3c8f3d9904a7a90290434b4496ebf154f18b673cc816fd0f144c6
|
|
BLAKE2b-256 checksum How to use checksums |
48a114f637dad292da21114263d8015f69685ded4380f83c5d58721dbb60615f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp314-cpwin_amd64-win_amd64.whl
| Download URL | doppler_dsp-0.59.0-cp314-cpwin_amd64-win_amd64.whl |
|---|---|
| Size | 7.3 MB |
| Tags | CPython 3.14 CPython w.in_amd64 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
bbc2cf1b41ac83713e4aafc9163bca0b264a75c70b654059d6d50f1a9d94abd6
|
|
BLAKE2b-256 checksum How to use checksums |
5d7e75810ba99d1f4d0807fa7574807ca8c2b2438b4cd35c0648596d1f47d62f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | doppler_dsp-0.59.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 8.1 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
ba283993af6ddf52b51f1e7f3db0f203766ed657afdec7bdbd6e3d875f8832be
|
|
BLAKE2b-256 checksum How to use checksums |
0ce3fe23617785edb065aaf65a5afdd34d50863245ce79bed91ccc12c70144a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp314-cp314-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | doppler_dsp-0.59.0-cp314-cp314-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.0 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
9aa4ed0e7f18c3de984f5f7308aa92f9c8495acd0f105594d95f85939aa7cad8
|
|
BLAKE2b-256 checksum How to use checksums |
53c94c88154dd70d3f2add443a03eb17343e6ac8faca32d912645c383db68484
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | doppler_dsp-0.59.0-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 7.4 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
22b87d207ea2e685c0e688bbc7d51aaa0b09cc5e32f2f845af70caa225af3286
|
|
BLAKE2b-256 checksum How to use checksums |
e5817952cd4d5959bb13b6b566f6b979c50abe15a7155d851e6df5555976cc55
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp313-cpwin_amd64-win_amd64.whl
| Download URL | doppler_dsp-0.59.0-cp313-cpwin_amd64-win_amd64.whl |
|---|---|
| Size | 7.2 MB |
| Tags | CPython 3.13 CPython w.in_amd64 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
a53ba73c51ff8cd17671e1aaa903aee6ba9b1f244ee752a306daaa63a0b497e6
|
|
BLAKE2b-256 checksum How to use checksums |
063504c35176d036c345c43a2c747505ace80833c172e0da1c03df6e18f26e59
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | doppler_dsp-0.59.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 8.1 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
dee761e03be3e1a6b862df1139beb269486c90dbc4ad3effacdd476970eb8de1
|
|
BLAKE2b-256 checksum How to use checksums |
180d0af30e037a8f009b9a5a56f38c99b27421083a386d111870afd9f9bf3135
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | doppler_dsp-0.59.0-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.0 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
fa35d1b867be1682397b6cd9097ce0588784e0cbc6972084de1a851263607f2e
|
|
BLAKE2b-256 checksum How to use checksums |
2750ec400deabd5614f0a19cc303ed3521a33e668f8c5c01b6d16feb98d91263
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | doppler_dsp-0.59.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 7.4 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a994c41e1490a471f878a8dcf678945db6f9df2a28a5f5996a72897828ea657a
|
|
BLAKE2b-256 checksum How to use checksums |
2a1f593500fce4f5c70278693cf802512d14ec63c5afc6cd7f23bf29a10422f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp312-cp312-win_amd64.whl
| Download URL | doppler_dsp-0.59.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 7.1 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
8da7ae7fdc0fd368dae6c20bed0faa5d5faa95a8cbc71d07e0cd9f03c800350e
|
|
BLAKE2b-256 checksum How to use checksums |
c45f7dc7af00a44d44bb2ffba28c6fa19647c091fbadc0100558b9e731059cd4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | doppler_dsp-0.59.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 8.1 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
7041819cab75b876cbeacca8ec246d72e51b58c5b82bc40b015477b84be741b7
|
|
BLAKE2b-256 checksum How to use checksums |
fe82fa53a852d9ffd752258792833117d1ff92df1115955e7c31849b3285f2ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | doppler_dsp-0.59.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.0 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
0ea7eee8d4f163a490e45536d7356eaebc01a5b09295cdfa2b080e1c9e585311
|
|
BLAKE2b-256 checksum How to use checksums |
7e5ba7fd63923cf0090e3889bd02abd813fe99856a642b9c30412e02e705a2dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | doppler_dsp-0.59.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 7.4 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
bfdd17a4f3a7048dea7593863063b2a265e3cd8d415044a804599fdd7425c65c
|
|
BLAKE2b-256 checksum How to use checksums |
926a1c768724aaa97cbdd239339effb07ee68015eaa74d5f0d9c0cfb2561a138
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp311-cp311-win_amd64.whl
| Download URL | doppler_dsp-0.59.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 7.1 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
a72c0beff7cedfbd59b28b681b519ead8a3ab81de4b5c0d7064bee99390f61a8
|
|
BLAKE2b-256 checksum How to use checksums |
a54fbb4c8c428979b9144eab7da0bbd1b68054acbd099637387f2ad22032fc12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | doppler_dsp-0.59.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 8.0 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
9095c30679fa4f10b9bd4fe582aaa3e984d2397a377966683a88c2077757780b
|
|
BLAKE2b-256 checksum How to use checksums |
4200aa13a4402f78b03a4a46ff25a5646b8e3e4cb7e1b35cd8615d537e7f8f98
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | doppler_dsp-0.59.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.0 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
1f15adfe833637242fa614510c12f8239794051b1b7d7f8c0bb09dc44e931668
|
|
BLAKE2b-256 checksum How to use checksums |
874c713e1f8b8bb51469d4ba5441342c3e2e8ac205df278e69619be69782359b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | doppler_dsp-0.59.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 7.4 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
98232ec96f79b72f028ec17239bd0f9475a947384b353741ff1f385221258e0f
|
|
BLAKE2b-256 checksum How to use checksums |
d967bbb69b6469b3024017b62baface49f5079fbfd1049859ddc22388438738d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp310-cp310-win_amd64.whl
| Download URL | doppler_dsp-0.59.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 7.1 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
accdeeb1e6e996b1e3343e2afe02fec6afe79dcf3ce7e1e34ce84b0cabe15376
|
|
BLAKE2b-256 checksum How to use checksums |
6cb653203bd0b713c62340955eb0319b508ce5d77767e7c5b0d2aa0dc47a9481
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | doppler_dsp-0.59.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 8.0 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
2f032a057b2ff3afb5c98c7f06f3a6efae0a84f74a0a96d3e320b4c601185e01
|
|
BLAKE2b-256 checksum How to use checksums |
aa8fa8abf2e7315d0bb062fd534fbacaf10d43850ab8663886443be8e1ba185c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | doppler_dsp-0.59.0-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.0 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
2cca731875ded18774bcf04f84a8219da020f9f5d3ad41477de8d3cd5bea13f4
|
|
BLAKE2b-256 checksum How to use checksums |
b3626ede713f906a2379582d74c64874dfff227b5704f27c9222ccc78674f8a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | doppler_dsp-0.59.0-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 7.4 MB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
3603a44ce1adc9361b530e843241196c0e89eb3d78a3ad7e46e97febb3beb648
|
|
BLAKE2b-256 checksum How to use checksums |
f6821ca025cbd4dbebaee4267cb710ca95a6b4918f9ad0a32e75e497ac4e9dca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp39-cp39-win_amd64.whl
| Download URL | doppler_dsp-0.59.0-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 7.1 MB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
74df29ad05d989fc2ae0eca719cb1c811ab3900bfee0ce77014e4ab649ebf1ba
|
|
BLAKE2b-256 checksum How to use checksums |
8e1b03180e3fc7753ab174088ad7e350a48236e3b2f162f8b8472be4453f1c50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | doppler_dsp-0.59.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 8.1 MB |
| Tags | CPython 3.9 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
f8412a8f10426aa6b8034dc9fab4d3ff1f43602326f4754049675af1af44bc92
|
|
BLAKE2b-256 checksum How to use checksums |
21991f99747b54f8ba4ec16ec32e2aca8ed21a8f204e2648b265bbecc559a402
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp39-cp39-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | doppler_dsp-0.59.0-cp39-cp39-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.0 MB |
| Tags | CPython 3.9 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
aeeb50fc628182087d9dd4059f44ac8f62858dfe0ef0eb4cb206b0e2fdbe535a
|
|
BLAKE2b-256 checksum How to use checksums |
52d26b37bcd6a56a508cb1165e7980ba2515f43a42710536e0b50cf807fab806
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / doppler_dsp-0.59.0-cp39-cp39-macosx_11_0_arm64.whl
| Download URL | doppler_dsp-0.59.0-cp39-cp39-macosx_11_0_arm64.whl |
|---|---|
| Size | 7.4 MB |
| Tags | CPython 3.9 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
2e03467b25df677add591093a5823d0b1ede52635f7a754bf43162811ba1b36e
|
|
BLAKE2b-256 checksum How to use checksums |
093e13fa79f61bc13788e390d9b6aef79e92a3f1b4fb46747f7500bad1cac497
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logSecurity for doppler-dsp 0.59.0
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 25 files in this release have been uploaded with provenance metadata.
Attestation for doppler_dsp-0.59.0.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 Sep 30, 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.
