The author of this package has not provided a project description
Metadata
Release files for ipynb-autograde 0.1.4
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 | |
|---|---|---|---|---|
| ipynb_autograde-0.1.4.tar.gz | 21.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ipynb_autograde-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 42.9 kB
Release files / ipynb_autograde-0.1.4.tar.gz
| Download URL | ipynb_autograde-0.1.4.tar.gz |
|---|---|
| Size | 21.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1a4db7c76542a371340bb9c58efd1fc4493de3bf4bec99a40a9e07215fa4a995
|
|
BLAKE2b-256 checksum How to use checksums |
fa35a91cc2eb8addb95756738af5107998a87146df8c92c828cc8a48060620bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.10.11
|
Release files / ipynb_autograde-0.1.4-py3-none-any.whl
| Download URL | ipynb_autograde-0.1.4-py3-none-any.whl |
|---|---|
| Size | 21.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
194441ba3855fe3513675cea1531c2e856c08b700ee6c6a6ff676f36f2be0a9f
|
|
BLAKE2b-256 checksum How to use checksums |
9e260e49cfa375474ff832a9a9ac0c0df385068d6aa22b716623f886d747cdd7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.10.11
|
Security for ipynb-autograde 0.1.4
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.