The author of this package has not provided a project description
2 maintainers
Metadata
2 maintainers
Release files for astrosat 1.0.1
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 | |
|---|---|---|---|---|
| astrosat-1.0.1.tar.gz | 584.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| astrosat-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / astrosat-1.0.1.tar.gz
| Download URL | astrosat-1.0.1.tar.gz |
|---|---|
| Size | 584.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
365b37a7af4d086a87e6dee91ab399412abbb1a2c5ed6aec47883562ba5ba8a2
|
|
BLAKE2b-256 checksum How to use checksums |
fc658db559b8c5457df1434c0336448636ec0501d75c230ac0fb18b373326047
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Release files / astrosat-1.0.1-py3-none-any.whl
| Download URL | astrosat-1.0.1-py3-none-any.whl |
|---|---|
| Size | 599.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
326d39318aa37bca01ed054a50541751416a628f64fc3cc30a224f875b89370c
|
|
BLAKE2b-256 checksum How to use checksums |
529c4ac8d6ae362d121a3a678ebd6a83cf40c7c42b0d4c4cf836831a506a2aa1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Security for astrosat 1.0.1
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.
