1 maintainer
Metadata
1 maintainer
Release files for cross-domain-engine 1.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 | |
|---|---|---|---|---|
| cross_domain_engine-1.0.0.tar.gz | 1.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cross_domain_engine-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.0 kB
Release files / cross_domain_engine-1.0.0.tar.gz
| Download URL | cross_domain_engine-1.0.0.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0a06a57e4010f06e604e08dd83b9ac0cd3aa47ca1bfe43503e18e9a2405537e
|
|
BLAKE2b-256 checksum How to use checksums |
195d7528edb97c953c1b7a5477fd3f7011ee0b48bc75c715a85dcd88276bde3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Release files / cross_domain_engine-1.0.0-py3-none-any.whl
| Download URL | cross_domain_engine-1.0.0-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4ef76c1619096f0ba526ad62f98ef37db51d1d4dc5cd234a60b448f151fbed53
|
|
BLAKE2b-256 checksum How to use checksums |
b898e27c0b6c35a6ea3bebb7f52ed7073e5eb4ec8c6a3c51e58fb77e88c6ac87
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.6
|
Security for cross-domain-engine 1.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.
