The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for arsenic-tools 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 | |
|---|---|---|---|---|
| arsenic_tools-0.1.0.tar.gz | 746 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| arsenic_tools-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.0 kB
Release files / arsenic_tools-0.1.0.tar.gz
| Download URL | arsenic_tools-0.1.0.tar.gz |
|---|---|
| Size | 746 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f9c37683082acedf8a89c05f4c0c0e39467ae40c8fe5705188e057d6c1ec46bf
|
|
BLAKE2b-256 checksum How to use checksums |
0edab0c5456ca16c0e7f8e7e43e4e8aaed7d576f475427fdbac85ffb2dde1205
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Release files / arsenic_tools-0.1.0-py3-none-any.whl
| Download URL | arsenic_tools-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f735b7b4df9796a267b07f91ed3b8e1f3c6a9ddc59cf6a546b42bb81be10d50
|
|
BLAKE2b-256 checksum How to use checksums |
a87ef9e1aebfb124856f2e000aa05fcb3c56abfbacb8a2bfdd5564317329f2f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Security for arsenic-tools 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.
