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