sMRIprep is a structural magnetic resonance image pre-processing pipeline that is designed to provide an easily accessible, state-of-the-art interface that is robust to differences in scan acquisition protocols and that requires minimal user input, while providing easily interpretable and comprehensive error and output reporting.
This is a lightweight Python wrapper to run sMRIPrep. It generates the appropriate Docker commands, providing an intuitive interface to running the sMRIPrep workflow in a Docker environment. Docker must be installed and running. This can be checked running
docker info
Please report any feedback to our GitHub repository and do not forget to credit all the authors of software that sMRIPrep uses.
Release files for smriprep-docker 0.20.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 | |
|---|---|---|---|---|
| smriprep_docker-0.20.0.tar.gz | 8.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| smriprep_docker-0.20.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 17.0 kB
Release files / smriprep_docker-0.20.0.tar.gz
| Download URL | smriprep_docker-0.20.0.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
634ba1a7d72933ce72fd21683772ca23cc5dec62f1759183a477fe284b7eb4db
|
|
BLAKE2b-256 checksum How to use checksums |
92d19b8b53f556bb74ddda94b2e7723a0e81c912ff8d12cf24f1c1a73a5bca9d
|
| 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 Aug 25, 2026.
Transparency logRelease files / smriprep_docker-0.20.0-py2.py3-none-any.whl
| Download URL | smriprep_docker-0.20.0-py2.py3-none-any.whl |
|---|---|
| Size | 8.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
14474001e7b00f6fe4f7f7aa98ddb3acf59618d90d17b8b954fce33198d61ed1
|
|
BLAKE2b-256 checksum How to use checksums |
ae35e7c8ec18f6dcd1255f90af6fe814745c7a354420d02fa55d3b4a4900a660
|
| 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 Aug 25, 2026.
Transparency logSecurity for smriprep-docker 0.20.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 2 files in this release have been uploaded with provenance metadata.
Attestation for smriprep_docker-0.20.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 Aug 25, 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.
