🚧 This project is in active beta development. This means the API is unstable, features may be added or removed, and breaking changes are likely to occur frequently and without notice as the design is refined.
Chrono Batch Render
Chrono Batch Render is a physically-based, real-time, spectral renderer for planetary robotics and sensing.
It is cross-platform and designed with portability in mind, supporting Linux, Windows, and macOS with C++ and Python APIs, and both hardware and software ray tracing support across NVIDIA and AMD GPUs and Apple silicon.
The scene description is modeled on OpenUSD. It is schema-driven with prims at hierarchical paths that have attributes. Unlike OpenUSD, the scene lives on the GPU by design, so render outputs and scene data can be shared zero-copy with other GPU-accelerated applications.
Chrono Batch Render is also built to fit into other applications, whether that's visualizing a physics simulation, rendering large-scale terrain or simulating high-fidelity sensors. It offers fast interfaces behind a simple API, and the bundled viewer is easy to customize for your own application.
A brief overview of its features:
- Extensible: custom materials, BRDFs, and sensor filters
- Configurable fidelity: built-in rendering modes ranging from low-fidelity RL high-throughput cases to predictive spectral path tracing
- Zero-copy tensors: render outputs and scene data (transforms, vertices, lights) are shared via DLPack with PyTorch, JAX, Warp and Numpy
- Batched rendering: many sensors and worlds rendered in one step for RL
- Spectral light: 8 bands spread over each camera's own spectral range, from the visible to thermal infrared, with RGB inputs uplifted to spectra
- Physical lighting: distant, dome, rect, disk, cylinder and sphere lights in physical units (nits, lux or lumens), with blackbody, CIE daylight or measured illuminant spectra, IES profiles and light linking
- Materials: UsdPreviewSurface with normal and detail maps and triplanar projection, Lambert and GGX lobes, ITU-R P.2040 radar materials, and your own materials in Slang
- Cameras: perspective, orthographic and spherical projections, Brown-Conrady, Kannala-Brandt, f-theta and lookup-table lens distortion, and depth of field
- Optics and detector effects: diffraction, glare, blooming and vignetting, EMVA 1288 sensor noise, Bayer, RCCB and RCCC mosaics, demosaicing, auto exposure and tone mapping, with your own filters in Slang
- Thermal infrared: Planck emission with emissivity from Kirchhoff's law, and temperatures per prim or per vertex and face from your solver
- Precision at any scale: double-precision transforms and a camera-relative render origin for each world
- OpenXR: OpenXR headsets with controllers, haptics, hand and eye tracking, pointers and smooth, grounded or fly locomotion, plus a simulated headset for testing without hardware, from C++, Python or the viewer's XR panel
- Benchmarks: a harness that renders the same scenes through Chrono Batch Render, Newton, NVIDIA's ovrtx and Madrona under the same timing rules, measuring throughput and scaling
For a more detailed overview of the features, see our documentation.
Future work:
- Integrations into Chrono Sensor, Newton Viewer and Isaac Lab
- OpenUSD and glTF support, plus 3D Tiles, OpenPBR, MaterialX and MDL
- Virtual textures and paging techniques
- Terrain level-of-detail
- Laser lights for structured light
- Reflections and global illumination
- Volumetric rendering
- Motion blur and rolling shutter
- Atmospheres
- Gaussian splat and particle fields
- Animation and skinning
- Differentiable rendering
- Spectral benchmarks, with Mitsuba 3's spectral variants as the reference and ovrtx's spectral mode as a comparison
Quick Start
We recommend installing Chrono Batch Render from PyPI. We also ship a GUI application that provides interactive viewing and editing of scenes. The following commands install Chrono Batch Render, check that it installed successfully and open the GUI.
pip install chrono-batch-render
python -c "import chrono_batch_render; print(chrono_batch_render.__version__)"
chrono-batch-render # Opens the GUI
In Python, basic API usage involves creating a Scene with some objects. Then creating a Renderer with that Scene and calling Renderer.step with the desired render products. See below for an example.
import chrono_batch_render
scene = chrono_batch_render.Scene()
chrono_batch_render.Plane.define(
scene,
"/Ground",
width=20,
length=20,
checkerboard=True,
)
chrono_batch_render.Cube.define(
scene,
"/Box",
translate=(-1.5, 0, 0.75),
size=1.5,
display_color=(0.8, 0.2, 0.2),
)
chrono_batch_render.Cylinder.define(
scene,
"/Post",
translate=(1.5, 1, 1),
radius=0.4,
height=2,
display_color=(0.2, 0.4, 0.8),
)
ball = chrono_batch_render.Sphere.define(
scene,
"/Ball",
radius=0.5,
display_color=(0.9, 0.8, 0.2),
semantics_labels={"class": ["ball"]},
)
chrono_batch_render.DistantLight.define(
scene,
"/Sun",
orient=chrono_batch_render.from_azimuth_elevation(135, 45),
intensity=50000,
)
chrono_batch_render.Camera.define(
scene,
"/Front",
translate=(0, -9, 5),
orient=chrono_batch_render.look_at((0, -9, 5), (0, 0, 0.5)),
focal_length=35,
)
chrono_batch_render.Camera.define(
scene,
"/Top",
translate=(0, 0, 14),
orient=chrono_batch_render.look_at((0, 0, 14), (0, 0, 0), up=(0, 1, 0)),
focal_length=24,
)
chrono_batch_render.GradientBackground.define(scene, "/Sky")
chrono_batch_render.Scope.define(scene, "/Render")
chrono_batch_render.RenderVar.define(scene, "/Render/Color", source_name="LdrColor")
chrono_batch_render.RenderVar.define(scene, "/Render/Depth", source_name="DistanceToCamera")
chrono_batch_render.RenderVar.define(scene, "/Render/Normal", source_name="Normal")
chrono_batch_render.RenderVar.define(scene, "/Render/Semantic", source_name="SemanticSegmentation")
chrono_batch_render.RenderProduct.define(
scene,
"/Render/Views",
camera=["/Front", "/Top"],
resolution=(640, 480),
ordered_vars=["/Render/Color", "/Render/Depth", "/Render/Normal", "/Render/Semantic"],
render_mode="RealTime",
background="/Sky",
)
renderer = chrono_batch_render.Renderer(scene)
for step in range(4):
ball.translate = (step - 1.5, -1.5, 0.5)
scene.advance(1 / 30)
output = renderer.step(["/Render/Views"])
output.wait()
[frame] = output["/Render/Views"].frames
for var in frame.render_vars:
aov = frame.render_var(var)
for camera, name in enumerate(["front", "top"]):
chrono_batch_render.write_render_var(f"{name}_{aov.source_name}_{step}", aov, camera)
| Color | Depth | Normal | Semantic | |
|---|---|---|---|---|
| Front | ||||
| Top |
For more advanced code snippets and API usage such as zero-copy interop, batched rendering, cloning, and custom materials see our guides.
For more information about Chrono Batch Render's requirements, Python and C++ installation, or other installation methods such as Docker and building from source, see our installation guide.
Citation
If you use Chrono Batch Render in your research, please cite it. GitHub's "Cite this repository" button gives the same citation from CITATION.cff.
@software{maietta2026chronobatchrender,
author = {Maietta, Alex},
title = {Chrono Batch Render},
year = {2026},
version = {0.1.0},
url = {https://github.com/uwsbel/chrono-batch-render},
license = {BSD-3-Clause}
}
License
Chrono Batch Render is licensed under the BSD 3-Clause License.
Acknowledgements
Chrono Batch Render is built on these open-source projects.
- Vulkan Headers, volk and Vulkan Memory Allocator for the GPU layer
- Slang for shaders
- DLPack for sharing tensors with PyTorch, JAX, Warp and NumPy
- nanobind for the Python bindings
- OpenEXR and Imath, stb, Basis Universal and bc7enc_rdo for images and textures
- NanoVDB for volumes
- nlohmann/json for JSON
- {fmt} for text formatting
- tinyobjloader for OBJ import
- MikkTSpace for tangents
- NVTX for profiling
- OpenUSD for scene interchange
- Dear ImGui and GLFW for the viewer
- GoogleTest for tests
- Google Benchmark for benchmarks
Chrono Batch Render also leverages ideas from these renderers and projects:
- Madrona for batch rendering across many worlds
- Chrono::Sensor for sensor simulation inside Chrono
- Cycles, Mitsuba 3 and PBRT for physically based and spectral rendering
- OpenUSD and Omniverse Fabric for the schema-based scene
- ovrtx for zero-copy interops and USD-based rendering
- nvpro-samples for Vulkan ray tracing and cluster LOD
- PANGU for planetary and asteroid surface simulation
- IRIS for real-time, closed-loop rendering of space sensors
- CosmoScout VR for planet-scale scenes and solar-system visualization
- three-geospatial for atmospheres and clouds
- Isaac Lab and Newton for tiled cameras in robot learning
Metadata
Release files for chrono-batch-render 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 | Actions |
|---|---|---|---|---|
| chrono_batch_render-0.1.0.tar.gz | 1.5 MB | With provenance | Details for chrono_batch_render-0.1.0.tar.gz |
Built distributions (wheels)
Total release size: 402.9 MB
Release files / chrono_batch_render-0.1.0.tar.gz
| Download URL | chrono_batch_render-0.1.0.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9b714b24627dd78e792f07b4a8d6e9107b6143f9e6b0887de59c1b8e5c8b86b
|
|
BLAKE2b-256 checksum How to use checksums |
c8e91d43a54050279e8a49521b5d56270bc5d600a7e05a3e47aaaf4db247c215
|
| 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 Nov 12, 2026.
Transparency logRelease files / chrono_batch_render-0.1.0-cp312-abi3-win_arm64.whl
| Download URL | chrono_batch_render-0.1.0-cp312-abi3-win_arm64.whl |
|---|---|
| Size | 21.8 MB |
| Tags | CPython 3.12 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
e29822dfe480d137b60e1af745782e387388041185620dfef0ab169fd44c2bee
|
|
BLAKE2b-256 checksum How to use checksums |
d811d976a27a9377575b0947674d070aa1dce2613d389daad7532a988e940f9e
|
| 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 Nov 12, 2026.
Transparency logRelease files / chrono_batch_render-0.1.0-cp312-abi3-win_amd64.whl
| Download URL | chrono_batch_render-0.1.0-cp312-abi3-win_amd64.whl |
|---|---|
| Size | 22.4 MB |
| Tags | CPython 3.12 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
8f0da9f62250ba5bcd3fdd7514f5d2e7715561949e1032d3a0ad6e20c478973e
|
|
BLAKE2b-256 checksum How to use checksums |
17de1cf39f0ae8e805db1f47f45cb71ee0b8ac97bffac9c4b956cc28bb1c132a
|
| 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 Nov 12, 2026.
Transparency logRelease files / chrono_batch_render-0.1.0-cp312-abi3-manylinux_2_34_x86_64.whl
| Download URL | chrono_batch_render-0.1.0-cp312-abi3-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 30.5 MB |
| Tags | CPython 3.12 Linux glibc 2.34+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
fbdbe4eaa6ff5432cd32fd6a91eaa24aea38bd94b30fd29a04d013811925654e
|
|
BLAKE2b-256 checksum How to use checksums |
cf717ffd876f620908109dc4ad98b33c4757e8e56bd83b0382868dad0b349420
|
| 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 Nov 12, 2026.
Transparency logRelease files / chrono_batch_render-0.1.0-cp312-abi3-manylinux_2_34_aarch64.whl
| Download URL | chrono_batch_render-0.1.0-cp312-abi3-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 29.0 MB |
| Tags | CPython 3.12 Linux glibc 2.34+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
3642bcc93d66e1cd0cf9a1f1d9dff3ef2cb2e5f5eca7f2b7e1115119a429e32e
|
|
BLAKE2b-256 checksum How to use checksums |
3e059f9f641d30ebf3febb53c625f228d94319a6c3d621d54088ee1a39235fc5
|
| 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 Nov 12, 2026.
Transparency logRelease files / chrono_batch_render-0.1.0-cp312-abi3-macosx_26_0_arm64.whl
| Download URL | chrono_batch_render-0.1.0-cp312-abi3-macosx_26_0_arm64.whl |
|---|---|
| Size | 37.4 MB |
| Tags | CPython 3.12 abi3 macOS 26.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d13b073dfe637f3d3850c40ae14463e9f4b8b7ad76db905497284f26503af1a5
|
|
BLAKE2b-256 checksum How to use checksums |
517fa7292f51f997a86650e5f3d624d31e092c8b0eb57d046d5089a1e9dab323
|
| 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 Nov 12, 2026.
Transparency logRelease files / chrono_batch_render-0.1.0-cp311-cp311-win_arm64.whl
| Download URL | chrono_batch_render-0.1.0-cp311-cp311-win_arm64.whl |
|---|---|
| Size | 21.8 MB |
| Tags | CPython 3.11 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
17049f429c84849513533d6f9260524b2011e4225bef97fd7c46e24e1dbc9d5b
|
|
BLAKE2b-256 checksum How to use checksums |
f2cd884c6ac74c0687918d4a9ed7dfc259e66eef23d73aa837ba8976267f8765
|
| 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 Nov 12, 2026.
Transparency logRelease files / chrono_batch_render-0.1.0-cp311-cp311-win_amd64.whl
| Download URL | chrono_batch_render-0.1.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 22.4 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
de9a3a1c105bfaab09bf79255d07c87321131303918d19d5cf7800a1dff276e9
|
|
BLAKE2b-256 checksum How to use checksums |
4d0e8e71bc2f26abf06904447eb6b157449a88491baec39355906af3b36200f4
|
| 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 Nov 12, 2026.
Transparency logRelease files / chrono_batch_render-0.1.0-cp311-cp311-manylinux_2_34_x86_64.whl
| Download URL | chrono_batch_render-0.1.0-cp311-cp311-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 30.5 MB |
| Tags | CPython 3.11 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
d605d57d5de77b5469758e854cc1ba594b54d4a3dd0a13467ad010ad8cd7335d
|
|
BLAKE2b-256 checksum How to use checksums |
72a9336c300b781b98ba37533514398d3dfa8265712b20aec5b0621e444b1eee
|
| 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 Nov 12, 2026.
Transparency logRelease files / chrono_batch_render-0.1.0-cp311-cp311-manylinux_2_34_aarch64.whl
| Download URL | chrono_batch_render-0.1.0-cp311-cp311-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 29.0 MB |
| Tags | CPython 3.11 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
e7128deca8d6a0cc513ac436cf23cb7704f2d23daee5719f6c1959104155020b
|
|
BLAKE2b-256 checksum How to use checksums |
f225861484f2e4363256618c2d09035ce96e7ec4ce9af5dfa16a5679a8a3aeca
|
| 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 Nov 12, 2026.
Transparency logRelease files / chrono_batch_render-0.1.0-cp311-cp311-macosx_26_0_arm64.whl
| Download URL | chrono_batch_render-0.1.0-cp311-cp311-macosx_26_0_arm64.whl |
|---|---|
| Size | 37.4 MB |
| Tags | CPython 3.11 macOS 26.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
81cbaf9c3a6eca43c8f8f732fdc1ce8e24a7896514a6a56d94d6410705ee0ef4
|
|
BLAKE2b-256 checksum How to use checksums |
e057649c2552bf749c6b67c843305c67b83fbb05f0e7c6278f48f0f7a3988509
|
| 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 Nov 12, 2026.
Transparency logRelease files / chrono_batch_render-0.1.0-cp310-cp310-win_amd64.whl
| Download URL | chrono_batch_render-0.1.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 22.4 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
fb0a2de36ec612373c4e874370d671d8ffc78ee8082b29c64fa308256cc5f293
|
|
BLAKE2b-256 checksum How to use checksums |
ece95443f59bf14af533389eaf22a752d3f2d2ce100935fa016d0e65cdd17fc1
|
| 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 Nov 12, 2026.
Transparency logRelease files / chrono_batch_render-0.1.0-cp310-cp310-manylinux_2_34_x86_64.whl
| Download URL | chrono_batch_render-0.1.0-cp310-cp310-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 30.5 MB |
| Tags | CPython 3.10 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
0afdaaafe40e38b11a0eb8048db952bdf38f16576e7e0ce9b9555599be256f82
|
|
BLAKE2b-256 checksum How to use checksums |
44f23393eb4ddea6b5c6d72cd9b1bf35565bf0207e873875727016062d156c89
|
| 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 Nov 12, 2026.
Transparency logRelease files / chrono_batch_render-0.1.0-cp310-cp310-manylinux_2_34_aarch64.whl
| Download URL | chrono_batch_render-0.1.0-cp310-cp310-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 29.0 MB |
| Tags | CPython 3.10 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
b64d9f3a7403ddfa6620e493a98c8f5042c02df719c2b419d419d28efc5144e3
|
|
BLAKE2b-256 checksum How to use checksums |
4c85e653ce9fba1382731ddf523cb2c410909f817cd6fc70da9c5d97d9305948
|
| 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 Nov 12, 2026.
Transparency logRelease files / chrono_batch_render-0.1.0-cp310-cp310-macosx_26_0_arm64.whl
| Download URL | chrono_batch_render-0.1.0-cp310-cp310-macosx_26_0_arm64.whl |
|---|---|
| Size | 37.4 MB |
| Tags | CPython 3.10 macOS 26.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
f5b88eaae36308e1248be684bba9264be101bb48ac6cf2400745fb3aa48a6eb8
|
|
BLAKE2b-256 checksum How to use checksums |
47cfea09206e7cd615e21cb01a25be7ead406b37cb58b0aec8908314f6fb1435
|
| 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 Nov 12, 2026.
Transparency logSecurity for chrono-batch-render 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 15 files in this release have been uploaded with provenance metadata.
Attestation for chrono_batch_render-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 Nov 12, 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.