The author of this package has not provided a project description
2 maintainers
Metadata
2 maintainers
Release files for powerschool-alchemy 0.0.17
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 | |
|---|---|---|---|---|
| powerschool_alchemy-0.0.17.tar.gz | 5.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| powerschool_alchemy-0.0.17-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.6 kB
Release files / powerschool_alchemy-0.0.17.tar.gz
| Download URL | powerschool_alchemy-0.0.17.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32d140c516fae43ca204cb32504c01cd273a2af2342edc6ff7ba045fad5f14b5
|
|
BLAKE2b-256 checksum How to use checksums |
37709a4e20301d66cb270f3aa880ac8a23d04ffc8c1107a116f2dd1756421a3e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / powerschool_alchemy-0.0.17-py3-none-any.whl
| Download URL | powerschool_alchemy-0.0.17-py3-none-any.whl |
|---|---|
| Size | 16.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
48c0ae63f79a56567c20b3e17c0d3bd574fe464ad3b07dd9f50976a684ff1c69
|
|
BLAKE2b-256 checksum How to use checksums |
a95e766aa34a84dd55d33d3fd8fb20a0b72b8fae48d751f55f56cc59d24601a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for powerschool-alchemy 0.0.17
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.
