1 maintainer
Metadata
1 maintainer
Release files for autodiff-team44 0.1.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 | |
|---|---|---|---|---|
| autodiff_team44-0.1.0.tar.gz | 8.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autodiff_team44-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.5 kB
Release files / autodiff_team44-0.1.0.tar.gz
| Download URL | autodiff_team44-0.1.0.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2acea3d2bfd079895c3ac724be4af4c16ac4057760407a00e3f50d0bc405411
|
|
BLAKE2b-256 checksum How to use checksums |
9af2c93de02b5beb592f686802ef33033d59858e2359fbcd12f99b3b3821632b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.12
|
Release files / autodiff_team44-0.1.0-py3-none-any.whl
| Download URL | autodiff_team44-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e0aa81a625cb8a5f9b512219d46b01b98f4ccd9f9c411cd8d6117f57201ce2dd
|
|
BLAKE2b-256 checksum How to use checksums |
801374d4895547c86e8278edc42dceb362b7621f67c6eff746118c87b7d8cec0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.12
|
Security for autodiff-team44 0.1.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.
