2 maintainers
Metadata
2 maintainers
Release files for believing-machine 0.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 | |
|---|---|---|---|---|
| believing_machine-0.0.1.tar.gz | 6.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| believing_machine-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.1 kB
Release files / believing_machine-0.0.1.tar.gz
| Download URL | believing_machine-0.0.1.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
abb144996d6f7366df3e67ef4262d5c07baf3d3e1204f09dfd226863adcdac53
|
|
BLAKE2b-256 checksum How to use checksums |
6c91a4427d7e25bad3d84b355e64ea024170c2e64be9f401913ffaf0ed93894f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / believing_machine-0.0.1-py3-none-any.whl
| Download URL | believing_machine-0.0.1-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2b03cba030a3b8cc8a0770f4057bf097fd238f90e6f9c9144318b386f847c65d
|
|
BLAKE2b-256 checksum How to use checksums |
9a80942b77171734af1c075aff0d6a067879fc9d845f143bdf31c47de5d345c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for believing-machine 0.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.
