The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for interoception 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 | |
|---|---|---|---|---|
| interoception-0.1.0.tar.gz | 494 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| interoception-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 kB
Release files / interoception-0.1.0.tar.gz
| Download URL | interoception-0.1.0.tar.gz |
|---|---|
| Size | 494 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e4400ae4a965d4f828acfe94e8e1208239093c4e9eb50df10a3140bda4e22128
|
|
BLAKE2b-256 checksum How to use checksums |
ec7deed0f56dba4672484ea2ed6f760170239612a7948038bb9c09fb7f22921c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.2
|
Release files / interoception-0.1.0-py3-none-any.whl
| Download URL | interoception-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e389cb2d65e7fe4401bfb2d02296d92295e4ee3da21fd14627ce228c95859ecb
|
|
BLAKE2b-256 checksum How to use checksums |
f7bb728a5a34546867ce31c21aeb741ea872ef8d71ddba06bdd8aa81d7f03a80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.2
|
Security for interoception 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.
