Skip to main content
Change of provenance

The repository or configuration that created this release differ from a previous release. View details.

memprobe

memprobe

Firmware memory budgets and size-regression checks for CI, from the command line.

memprobe demo

memprobe reads the section and symbol table from your ELF and sends only that metadata to the memprobe API. It sends the same sizes and symbol names readelf and nm print, nothing else.

pip install memprobe

Quick start

  1. Create an API key at https://memprobe.dev (Account, then API keys).

  2. Point the CLI at it:

    memprobe config set --key mp_live_xxxxxxxx
    
  3. Check a build against budgets:

    memprobe init            # writes a memprobe.toml with flash/ram budgets
    memprobe check build/firmware.elf
    

    check exits non-zero when a budget is exceeded, so it gates a CI job.

Commands

Command What it does
memprobe analyze <elf> Size summary: flash/ram totals, biggest sections and symbols.
memprobe check <elf> Fail (exit 1) if a budget or watched symbol limit in memprobe.toml is exceeded. The CI gate.
memprobe diff <old> <new> Size change between two builds, with per-file and per-symbol deltas. --format markdown for PR comments.
memprobe diff <elf> --project <name> Diff against the project's saved baseline build, no second file needed.
memprobe init Scaffold memprobe.toml with flash/ram budgets. --from-ld <script.ld> fills part capacity from the linker script.
memprobe account Show your plan and this month's usage.
memprobe config set --key <key> [--server <url>] Store your API key (in ~/.memprobe/config.json).
memprobe config show Show the current key (masked) and server.

MEMPROBE_API_KEY and MEMPROBE_SERVER override the stored config, for use in CI.

CI

Because memprobe check exits non-zero when a budget is exceeded, it works as a gate in any CI system. Run it as a build step with MEMPROBE_API_KEY set as a secret:

pip install memprobe
memprobe check build/firmware.elf

On GitHub, memprobe-action wraps this and also posts a size report with symbol-level changes as a PR comment:

- uses: memprobe-dev/memprobe-action@v1
  with:
    file: build/firmware.elf
    api-key: ${{ secrets.MEMPROBE_API_KEY }}

What runs where

Local (this tool) memprobe API
Reads your ELF yes never sees the binary
Extracts sections/symbols yes (via pyelftools) no
Budget / diff / bloat analysis no yes

This is a thin open-source client with no analysis logic of its own. The deeper analysis (call graph, dead code, stack usage, source attribution) runs in the web app at https://memprobe.dev.

License

MIT

Metadata

Release files for memprobe 0.1.4

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

Change of provenance

The repository or configuration that created these release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Source distribution (sdist)

Source distribution for memprobe 0.1.4
File Size Uploaded Provenance Actions
memprobe-0.1.4.tar.gz 17.5 kB With provenance Details for memprobe-0.1.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for memprobe 0.1.4
File Interpreter ABI Platform Actions
memprobe-0.1.4-py3-none-any.whl Python 3 none any Details for memprobe-0.1.4-py3-none-any.whl

Total release size: 33.1 kB

Release files / memprobe-0.1.4.tar.gz

Change of provenance

This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Download URL memprobe-0.1.4.tar.gz
Size 17.5 kB
Tags Source
SHA-256 checksum
How to use checksums
ca4fde417c74243a1d7074c06097d217b8eb0ec7d23e498df902deb7ca20175d
BLAKE2b-256 checksum
How to use checksums
8d010d0f7c60dce071164952bf0562d01ecccb11be3f34491987a6205c2a74b6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jun 21, 2026.

Transparency log

Release files / memprobe-0.1.4-py3-none-any.whl

Change of provenance

This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Download URL memprobe-0.1.4-py3-none-any.whl
Size 15.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
963cbd5c6924b27e0b69ec6c94abd10f09e05fa1d11f29c17432a3d479dab7a3
BLAKE2b-256 checksum
How to use checksums
d03a30e9febf41ff29ed34497cda88bc4f012595cf29eb4a67eeeae6bc4aea79
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jun 21, 2026.

Transparency log

Security for memprobe 0.1.4

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.

Change of provenance

The repository and configuration that created this release differ from a previous release.

While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.

Select from 2 files

Attestation for memprobe-0.1.4.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 Jun 21, 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