horizon-pulse
Name reserved by Horizon Pulse. See https://horizonpulse.dev
1 maintainer
Metadata
1 maintainer
Release files for horizon-pulse 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 | |
|---|---|---|---|---|
| horizon_pulse-0.0.1.tar.gz | 1.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| horizon_pulse-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.5 kB
Release files / horizon_pulse-0.0.1.tar.gz
| Download URL | horizon_pulse-0.0.1.tar.gz |
|---|---|
| Size | 1.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af5edb970b35a286258b43da3b99a6e365d69364126672f7905489eadb6558d6
|
|
BLAKE2b-256 checksum How to use checksums |
575310b326504ff4f743367b7c40e8f8a91cbbd63db5ddc78702cd89f771a802
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.5
|
Release files / horizon_pulse-0.0.1-py3-none-any.whl
| Download URL | horizon_pulse-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
10a6fb7279cf7591a5e63722369d6b0d1425e935af465f072b28995f1d2648ad
|
|
BLAKE2b-256 checksum How to use checksums |
d78007917b433a847ef59a68993f2de18ce32c271f621e538a5e55273e959624
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.5
|
Security for horizon-pulse 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.
