Original Science API documentation (Canvas internal)
ONC Criteria (Canvas internal)
1 maintainer
Metadata
1 maintainer
Release files for canvas-science 4.0.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 | |
|---|---|---|---|---|
| canvas-science-4.0.0.tar.gz | 693.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| canvas_science-4.0.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 1.4 MB
Release files / canvas-science-4.0.0.tar.gz
| Download URL | canvas-science-4.0.0.tar.gz |
|---|---|
| Size | 693.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
635c5fca6d3e71a478a5aa1aadcfd0485a870e810b11c85297e7e47a2c127cac
|
|
BLAKE2b-256 checksum How to use checksums |
720e47347184d62872072850e06a705a417d7ee2383104a5b1387ab58301bfc0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / canvas_science-4.0.0-py2.py3-none-any.whl
| Download URL | canvas_science-4.0.0-py2.py3-none-any.whl |
|---|---|
| Size | 716.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
71ce11fce00a04372199ba17bff7a09f180aaaa8649a59ae9edc9b59532a138a
|
|
BLAKE2b-256 checksum How to use checksums |
1e8bf9dfa5d2a93cd29e413ed38eeff6d6de231a2572ea20c59ba5555cd4d225
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for canvas-science 4.0.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.
