edge
Minimalistic C++20 rendering library with Vulkan, OpenGL ES 3.0 / WebGL 2 and Metal backends, and Python bindings (pyedge).
It has everything you need to load geometry, render it and develop your code in a platform and API independent manner.
It can read glTF and has an in-house fast-loading .edge format for models with support for LODs and mip chains.
It is meant to be read and changed: there is no scene editor, no scripting layer (except Python bindings) and no asset store.
It was refactored from a game engine from 2004 to render many scenes in parallel for robotics simulation (cameras, depth and lidar images for training and testing), where a general-purpose engine was too slow. Much of the binding code, refactorings, new backends and documentation were written with Claude and curated by the author. The library was also used successfully to build computer games which are running on MacOS, Windows, Linux, iOS, Android, and even web browsers.
Features
- Backends: Vulkan 1.0 with
VK_KHR_maintenance1(Linux, Windows, Android, macOS through MoltenVK), OpenGL ES 3.0 and WebGL 2 (Emscripten), Metal (Apple silicon, macOS 13 and iOS 15 on), and a null renderer that keeps every rule and draws nothing (for tests). The frame and pass order and the error behaviour are the same on every backend. - Headless and parallel: renderers share no state, so a process runs one per thread, each offscreen, on one GPU or several. Frames in flight (1 to 4), batched texture downloads, GPU timers.
- glTF 2.0: meshes, PBR metallic-roughness materials (normal, occlusion and emissive maps),
KHR_texture_transform, skins and animations (linear, step and cubic), vertex colours, several UV sets. Loading is strict: a malformed file is an error that names what is wrong. - The
.edgeformat andedge_convert: models converted ahead of time, with BC7 or ASTC textures and their mip chains, levels of detail (meshoptimizer), texture atlases (grid or xatlas), tiled ground meshes and pose bounds for skinned meshes. CMake helpers rebuild a model only when its inputs change. - Rendering: render targets with several colour attachments, layers and cube faces; readable depth and stencil; instancing; blended draws sorted back to front; levels of detail chosen by pixel error; frustum culling; debug lines; text (stb_truetype); a Dear ImGui renderer; a full-screen copy and a frame presenter for windows.
- Shaders: GLSL 4.50 compiled to SPIR-V, and translated for GLES and Metal at build time.
edge.glslis the binding contract a custom shader includes, with BRDF, material and skinning helpers beside it. - Python:
pyedge(nanobind) exposes renderers, models, materials, cameras and textures; downloads arrive as NumPy arrays, long calls release the GIL, and the module is built free-threaded for Python 3.14t. edge_shot: draws a model to a PNG, a contact sheet of many, or a window to inspect it.
Status
edge is developed for the author's own projects, which use it in production. The API still changes between versions; see CHANGELOG.md. Contributions are welcome: see CONTRIBUTING.md.
Requirements
- CMake 3.20 or newer, Ninja, a C++20 compiler (GCC 12, Clang 15, Apple Clang 15, MSVC 19.3x)
- rove, the math library, checked out beside edge (
../rove) or given with-DEDGE_ROVE_SOURCE_DIR=<path> - For Vulkan: the Vulkan headers and loader and
glslangValidator. Without them edge builds without the Vulkan backend. - For OpenGL ES (
-DEDGE_GLES=ON):GLES3/gl3.hand libGLESv3. For Metal: Xcode. - SDL3 for
edge_sdl(windows and contexts), Boost.Test for the tests, Python 3.9 or newer with NumPy and pytest for pyedge - Network access on the first configure: the other dependencies are fetched at pinned versions (see THIRD_PARTY.md)
Install
pip (pip install pyedge, Linux wheels), Git submodules beside rove, Conan, vcpkg, or installed from source:
docs/install.md has each, with the CMake that uses it:
add_subdirectory(rove)
add_subdirectory(edge) # or find_package(edge CONFIG REQUIRED)
target_link_libraries(my_app PRIVATE edge::edge) # brings rove, spdlog, cereal and Vulkan
edge_add_shaders(my_shaders DESTINATION ${CMAKE_BINARY_DIR}/shaders SOURCES src/sea.vert src/sea.frag)
edge_bundle_runtime(my_runtime DESTINATION ${CMAKE_BINARY_DIR}) # edge's shaders beside the binary
edge_convert_models(my_models SOURCE_DIR ${CMAKE_SOURCE_DIR}/assets DESTINATION ${CMAKE_BINARY_DIR}/models)
From Python, pip install pyedge, with wheels for Linux and macOS on Apple silicon. On Linux it needs the system's Vulkan loader, libvulkan.so.1
(apt install libvulkan1), even for the null backend, and a Vulkan driver to draw (any GPU's, or Mesa's lavapipe). On a Mac it draws with Metal. pyedge
has the Vulkan, Metal and null backends; OpenGL ES is C++ only. On Windows, build it from source
(docs/install.md).
Build and test
git clone https://github.com/mnvl/rove
git clone https://github.com/mnvl/edge
cmake -S edge -B edge/build -G Ninja -DCMAKE_BUILD_TYPE=RelWithDebInfo
cmake --build edge/build
ctest --test-dir edge/build -j$(nproc) --output-on-failure
On a real GPU run the Python tests one at a time (pytest without -n): two at once have lost the device on NVIDIA's driver. Set
VK_DRIVER_FILES to lavapipe's ICD to run them in parallel.
Without a GPU, Mesa's lavapipe (Vulkan) and llvmpipe (OpenGL ES) run the whole test suite on the CPU;
etc/container/test.sh builds and tests edge in such a Linux container.
A frame
#include <edge/camera.h>
#include <edge/load_model.h>
#include <edge/model.h>
#include <edge/scheduler.h>
#include <edge/vulkan_renderer.h>
auto renderer = std::make_shared<edge::VulkanRenderer>(640, 480);
auto scheduler = std::make_shared<edge::Scheduler>(renderer);
auto model = edge::load_model(renderer, scheduler, "robot.glb"); // a .glb, .gltf or .edge file
auto target = renderer->create_render_target(640, 480, edge::PixelFormat::A8R8G8B8);
auto camera = std::make_shared<edge::Camera>();
camera->set_perspective_projection(1.0f, 640.0f / 480.0f, 0.1f, 100.0f);
camera->look_at({0, 1, 4}, {0, 1, 0}, {0, 1, 0});
renderer->begin_frame();
model->draw(camera, rove::matrix<4, 4>()); // queues the model's draw calls
renderer->begin_pass(target); // cleared to black
scheduler->flush(); // sorted, culled, drawn
renderer->end_pass();
renderer->finish_frame(); // waits for the GPU: the target can be downloaded now
From Python the calls are the same (pyedge.create_renderer(640, 480), renderer.begin_frame(), ...), and a
downloaded texture is a NumPy array (texture.to_numpy()). examples/ has complete scripts.
Documentation
| docs/install.md | pip, Git submodules, Conan, vcpkg, installing from source |
| docs/building.md | Requirements, CMake options, the install tree, where shaders are found |
| docs/architecture.md | Conventions, the frame, backends, threads, design decisions |
| docs/coordinates.md | World and clip space, matrix order, the viewport flip, winding, pixel formats |
| docs/shaders.md | Writing shaders against edge.glsl |
| docs/render-targets.md | Targets of several colours, layers and cube faces |
| docs/models.md | Model types, ModelBuilder, the .edge format |
| docs/python.md | pyedge |
| docs/tools.md | edge_shot, edge_convert, CMake helpers for a game |
| docs/logging.md | The log and its levels |
The headers in src/ document each class and function.
License
MIT; see LICENSE. The libraries edge fetches when it is built are listed with their licenses in THIRD_PARTY.md.
Metadata
Release files for pyedge 3.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
Total release size: 33.9 MB
Release files / pyedge-3.0.1-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pyedge-3.0.1-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
77f7d0d5ea367fa31a630c3e82e59e0e22d706f4176103bf56f62ae85dff7ced
|
|
BLAKE2b-256 checksum How to use checksums |
db71d612e72b60822ceb93a206fcec93f175b6a2506e9d9e934da01483fabb57
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp314-cp314t-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pyedge-3.0.1-cp314-cp314t-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
ce0e758c2f512f97a1134ffbe9cc6570401757e3343b85c8c19889dab52558a7
|
|
BLAKE2b-256 checksum How to use checksums |
7eb8c4c8b60f342ad7190f85698da71a56e9baa7ceefcf1bdec7afbac9043a9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp314-cp314t-macosx_13_0_arm64.whl
| Download URL | pyedge-3.0.1-cp314-cp314t-macosx_13_0_arm64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 13.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a47eadc69708059f343ed9e422c3d39cf23dce81606cbaaeab3e090691d5415e
|
|
BLAKE2b-256 checksum How to use checksums |
3b03d593e00c10b2fbe2509968e09775d772cc22996903e44392f9acea471a5f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pyedge-3.0.1-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
9a2b6de6cca83a959f17fed2aebd18f673414193c7a3c0de75bd7c0bfb9bedcf
|
|
BLAKE2b-256 checksum How to use checksums |
55cf81e445773ab87ab3a8712c4a6eea277bf47705cea6456c668c58a5d94b12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp314-cp314-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pyedge-3.0.1-cp314-cp314-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
df3b8b2c80f71f9550cbee06c39b876d550696cbca403968f1888bc9865f6065
|
|
BLAKE2b-256 checksum How to use checksums |
196511179b66c90f7d418540ea40c655f5b9a03059a269b168b4bfb962643457
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp314-cp314-macosx_13_0_arm64.whl
| Download URL | pyedge-3.0.1-cp314-cp314-macosx_13_0_arm64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.14 macOS 13.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
207272cf95c4069732c6a482f056d88c99432ca641dcf8effb0214301d6a36e3
|
|
BLAKE2b-256 checksum How to use checksums |
ea10d9b9b598c65ee64c356c6a4de927849bf00c5e55b8b48ae32ec95bf20460
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pyedge-3.0.1-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
1f8bd839eadfb9146c88385a54d44eb2a5b05c4203b5aa42f2dd094a1697c7a2
|
|
BLAKE2b-256 checksum How to use checksums |
6b2f94ab8c64b54022412bca7c2fb370cb5d933942307ec2be1ed2c11147610d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pyedge-3.0.1-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
ae2bfdcddf5a1a70b967bf1c21ce6f7ba6ca039f4ffb0f8bf576d0747bb42343
|
|
BLAKE2b-256 checksum How to use checksums |
056e8d4a85217484e3006b1c098a33eb995b1724bb64d94a17bbfdd9a4b083f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp313-cp313-macosx_13_0_arm64.whl
| Download URL | pyedge-3.0.1-cp313-cp313-macosx_13_0_arm64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.13 macOS 13.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
4ebef2303f040f18999b6092c020c57f9c79ff2fc0f3d07b2c7cd9a01bddaea3
|
|
BLAKE2b-256 checksum How to use checksums |
ecd10be0b905924dcc86e472e7dc603ad6d8d64d30c56a6d84d5a323de708bfc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pyedge-3.0.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
b13dbf01177cccc2497fedcf9f10b8862a828695abfcadaa28a40f943e364832
|
|
BLAKE2b-256 checksum How to use checksums |
339c38737412b4be1d28ef21354c0ccd43101bbb68818c33ece2c64826617266
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pyedge-3.0.1-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
8d14aa23c51b4a5bd424d53fe61eee266b20c90101d51e977af75fef02fd30f3
|
|
BLAKE2b-256 checksum How to use checksums |
341d90dcefd7191fce72357f9a8d54d2ac945d5927055a5fa1da4537e82f2963
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp312-cp312-macosx_13_0_arm64.whl
| Download URL | pyedge-3.0.1-cp312-cp312-macosx_13_0_arm64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.12 macOS 13.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
2fff0e03b2968da82fa1b8ab088009cfdeec60bf32d34d776a9b1e5dbf5603a0
|
|
BLAKE2b-256 checksum How to use checksums |
de63995dd377a73598a1aa416248bc1862c0dff2f025b4e3be1c93165fbda841
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pyedge-3.0.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
6f98d321aede35455915933503b4f04f32612be1cfb222b87ae6c9db9b03c337
|
|
BLAKE2b-256 checksum How to use checksums |
d37d740afab503292c5aca085a0b11465345ab46ce649fa2128b22b2038eaee4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pyedge-3.0.1-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
98f505a4d40a86171960e81012016012eeda167a21d7e2851ecf76c9fc524cc0
|
|
BLAKE2b-256 checksum How to use checksums |
9ee0c5dd9104d9dd5c4f4a3860e628b2497914c42389eb4adace65a709ce2e66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp311-cp311-macosx_13_0_arm64.whl
| Download URL | pyedge-3.0.1-cp311-cp311-macosx_13_0_arm64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.11 macOS 13.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9bb48fb019e0091d95ecb1b3cf849bb22cb5e65308d91166228b864b2046b732
|
|
BLAKE2b-256 checksum How to use checksums |
0cda63eada482e3a6b43e4cde93284117e17c22a2e8591c22de40a80f536befa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pyedge-3.0.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
669fc9e5669ba36ba617860bc0c8a20a8466cc64a968ee9689f081ada592644f
|
|
BLAKE2b-256 checksum How to use checksums |
72b9aa90e0e64c0532fcdb2eddf6e61231ea285ebdef8b83a78e998a5abb2c04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pyedge-3.0.1-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
eb05eaa689dc8b11ee845c103991d211afc965ba4b1cfc71c0033d5edb7c8542
|
|
BLAKE2b-256 checksum How to use checksums |
c3517bc0c9ebebdcd15912123d85277f3aef934dc13091c0406dee760a6fc389
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp310-cp310-macosx_13_0_arm64.whl
| Download URL | pyedge-3.0.1-cp310-cp310-macosx_13_0_arm64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.10 macOS 13.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b85932b60bde7220d260a5236c482c1dfa684d596af04c909b6a1f11bebb36f4
|
|
BLAKE2b-256 checksum How to use checksums |
ab618059dcd4c267786c75ea085d6ac80adbba28902461a89658643f491e1854
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pyedge-3.0.1-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.9 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
e3590ee6c900a4b2ddb72b089aa0003eea11706f481cac94b7a39059dbb1e4e7
|
|
BLAKE2b-256 checksum How to use checksums |
75774fc7ad14a63f2b8ae5496adeaf3a5294225499bd297f30896f51c54b4e93
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp39-cp39-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pyedge-3.0.1-cp39-cp39-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.9 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
54e122a8f8ec83ba6bf9c5c4299be15a66a8f8e1781b0630df054705c0cbc60c
|
|
BLAKE2b-256 checksum How to use checksums |
a76eed53797e5a62c46e9fffb4287ca39b14297d1193d4c198ef7b9a214b7e4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / pyedge-3.0.1-cp39-cp39-macosx_13_0_arm64.whl
| Download URL | pyedge-3.0.1-cp39-cp39-macosx_13_0_arm64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.9 macOS 13.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0e546d902b0461b538e0ad59b2c35d1cab84e12df08259c1d2de1693d02dd3ac
|
|
BLAKE2b-256 checksum How to use checksums |
108b5a7826c784bc3a82af28793d9ca6cb548475a6c360a100046f0c92292941
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logSecurity for pyedge 3.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.
Full provenance
All 21 files in this release have been uploaded with provenance metadata.
Attestation for pyedge-3.0.1-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
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 Nov 7, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.