Metadata
Release files for factorio-circuit-ast 0.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 | |
|---|---|---|---|---|
| factorio-circuit-ast-0.0.0.tar.gz | 15.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| factorio_circuit_ast-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.1 kB
Release files / factorio-circuit-ast-0.0.0.tar.gz
| Download URL | factorio-circuit-ast-0.0.0.tar.gz |
|---|---|
| Size | 15.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f05f9530e8048c58c52e55fd958138866055859be9897cb34571a4b22da2b1e
|
|
BLAKE2b-256 checksum How to use checksums |
01afc771608710e4c9eab5ffd7ce2d02044cb7364c32be71d0dcf57c66b4f24f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.7
|
Release files / factorio_circuit_ast-0.0.0-py3-none-any.whl
| Download URL | factorio_circuit_ast-0.0.0-py3-none-any.whl |
|---|---|
| Size | 14.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
054dca8a8cd8be69ac8593c639ae4bf4336c160084169841caeb61bb269a4d9c
|
|
BLAKE2b-256 checksum How to use checksums |
3002d0d64997224bc2b78e73d4ddd549e6088b3603d8a4cfb0799510578436cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.7
|
Security for factorio-circuit-ast 0.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.