The author of this package has not provided a project description
Metadata
Release files for hcp2bids 0.2.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 | |
|---|---|---|---|---|
| hcp2bids-0.2.0.tar.gz | 8.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hcp2bids-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.5 kB
Release files / hcp2bids-0.2.0.tar.gz
| Download URL | hcp2bids-0.2.0.tar.gz |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d377da36add99f9a3c3737b1cc8a0f87aecb201e572b89abcd27e3248b730687
|
|
BLAKE2b-256 checksum How to use checksums |
48f4579b1717704d900a10c23c07bcc12124e40091345bfb9ad8ffa3f5d480f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.0b3 CPython/3.7.9 Darwin/19.6.0
|
Release files / hcp2bids-0.2.0-py3-none-any.whl
| Download URL | hcp2bids-0.2.0-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
690055caba3a7516ff2a7b9b269d28c2c9c70c6febee9319baaade52c94e6fb1
|
|
BLAKE2b-256 checksum How to use checksums |
8819cd2a2287a790480a424e9054dc866fe4841238ef8c8cbe58c9563e543b99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.0b3 CPython/3.7.9 Darwin/19.6.0
|
Security for hcp2bids 0.2.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.
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.