Metadata
1 maintainer
Release files for gvisor-sandboxexec 0.0.3
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 | |
|---|---|---|---|---|
| gvisor_sandboxexec-0.0.3.tar.gz | 4.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gvisor_sandboxexec-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.7 kB
Release files / gvisor_sandboxexec-0.0.3.tar.gz
| Download URL | gvisor_sandboxexec-0.0.3.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9128abd3a6cc842557638f65faaa245e5bca5fd7b2298480378b89438116da4d
|
|
BLAKE2b-256 checksum How to use checksums |
32e3608570aea642d280d864cc7e23fb6d8c7770a1dbf94cae6934e444623a34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Release files / gvisor_sandboxexec-0.0.3-py3-none-any.whl
| Download URL | gvisor_sandboxexec-0.0.3-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3a0c9077ddcf02dbc27aecb5fae92e48f62d8d305be3cd452ed34de1eac48bf9
|
|
BLAKE2b-256 checksum How to use checksums |
a66ad44023712e153574b419aa1f3e62516ff754f71be99fd2a5fa0798ab7b6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Security for gvisor-sandboxexec 0.0.3
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.
