Skip to main content

alloy-embedded

The CLI for the Alloy framework: one portable C++23 app source, any supported microcontroller — STM32 (G0/F7), SAM E70, RP2040, ESP32 — with zero #ifdefs.

uv tool install alloy-embedded      # installs the `alloy` command
alloy setup                          # verify/install toolchains (PATH-first)
alloy new blinky --board nucleo_g071rb
cd blinky && alloy run               # build + flash + serial monitor

The wheel embeds the framework (C++ runtime, board data) and depends on alloy-devices (the curated register/chip database).

Verbs, by task:

  • start — new, boards, chips, set-board, setup
  • build & run — build, flash, monitor, run, gen, clean, test
  • inspect — size, matrix, frame-audit, svd, debug-info
  • configure — board-info, board-validate, board-clone, chip-info, clock
  • emulate — emulate (headless Renode on a data-generated platform)
  • field update — keygen, image, ports, update (A/B slots, trial boot with rollback, optional Ed25519-signed images)
  • libraries — lib list | search | info | add

Most take --json for editor integration (versioned envelopes).

Docs: https://alloy-embedded.github.io/alloy/ · VS Code extension: alloy-vscode.

Metadata

Release files for alloy-embedded 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for alloy-embedded 0.3.0
File Interpreter ABI Platform
alloy_embedded-0.3.0-py3-none-any.whl Python 3 none any Details

Release files / alloy_embedded-0.3.0-py3-none-any.whl

Download URL alloy_embedded-0.3.0-py3-none-any.whl
Size 1.5 MB
Tags Python 3
SHA-256 checksum
How to use checksums
96672e8f4a0017ded7cd0508f045afa474efe8db429bd27007f2fdc320318064
BLAKE2b-256 checksum
How to use checksums
ab99d5e0c9e961d13cb1242ef04f3c57c54bcc5983847cef9ea114b440a25537
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 Aug 8, 2026.

Transparency log

Security for alloy-embedded 0.3.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 1 file in this release has been uploaded with provenance metadata.

Attestation for alloy_embedded-0.3.0-py3-none-any.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 Aug 8, 2026.

Transparency log

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page