safeloadai-runtime
The pinned CPython 3.12.0 for WASI that safeloadai
runs its sandbox in, shipped as package data. You do not install this package yourself:
pip install safeloadai pulls in the exact version it was tested with.
import safeloadai_runtime
safeloadai_runtime.path() # Path to python-3.12.0.wasm inside the installed package
safeloadai_runtime.SHA256 # pinned SHA-256 of that file
The package never downloads anything at install time or at run time. The binary is fetched once, when the package is built, and the build fails if its SHA-256 does not match. safeloadai checks the hash again, against its own pinned copy, before it uses the file.
Building:
python packages/safeloadai-runtime/fetch_runtime.py # download + verify (build machine only)
python -m build packages/safeloadai-runtime # refuses to build without a verified .wasm
Licences: CPython (PSF-2.0) and the VMware Wasm Labs WASI build (Apache-2.0). Details,
including the statically linked libraries, are in NOTICE and LICENSES/.
1 maintainer
Metadata
1 maintainer
Release files for safeloadai-runtime 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 | |
|---|---|---|---|---|
| safeloadai_runtime-0.1.0.tar.gz | 11.9 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| safeloadai_runtime-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.8 MB
Release files / safeloadai_runtime-0.1.0.tar.gz
| Download URL | safeloadai_runtime-0.1.0.tar.gz |
|---|---|
| Size | 11.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e297f4823785e3422c186a326c484346c8e0cd11fd59a4a4008d304ec013bf7b
|
|
BLAKE2b-256 checksum How to use checksums |
529a35aea4dcfc96d3c0745618b2de99c018c2de84b368e08b9dc20ed4b9367c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / safeloadai_runtime-0.1.0-py3-none-any.whl
| Download URL | safeloadai_runtime-0.1.0-py3-none-any.whl |
|---|---|
| Size | 11.9 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c3fab56da31d4ff4ff31a056c5482d201df3321cf52871b388ff326e64d29da3
|
|
BLAKE2b-256 checksum How to use checksums |
c29729189a7c8f31ac5c2f8887db98f256ff49b06ac6e980bfd8ce6982f7b209
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logSecurity for safeloadai-runtime 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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for safeloadai_runtime-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logA 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.
