BECK
Send your BIOS files to the right folders on your Recalbox, by matching them against the list of files it says are missing.
What it does
- Report: your Recalbox writes a list of the BIOS files it's missing, with the MD5 each one should have.
- Scan: BECK works out the MD5 of each file in your BIOS folder.
- Match: the name of your file doesn't matter, only its MD5.
- Copy: BECK sends each match over the network, under the name and into the folder your Recalbox expects.
Legal notice
BIOS files are copyrighted. BECK doesn't include, download or distribute them: it only matches files you already have. Only use BIOS dumps from hardware you own, and never commit BIOS files to this repository.
Install
BECK is on PyPI as beck-bios. With uv, which also gets the right
version of Python for you:
uv tool install beck-bios
Or with pipx, and Python 3.11 or newer:
pipx install beck-bios
Either way, you get a beck command. If your terminal can't find it, run uv tool update-shell or pipx ensurepath, and open a new terminal. Your Recalbox needs to be on your
network, with its SMB shares on, as they are on a fresh install.
Quick start
-
On your Recalbox, generate the report: main menu → BIOS CHECKING → REPORT.
-
On your computer, create your settings:
beck config init
They're ready for the usual Recalbox:
recalbox.local, with no password. If yours is different,beck config pathsays where the file is. Changeurlto use your Recalbox's IP address, as insmb://192.168.1.20/bios, and if it needs a login, setuser, and BECK asks for the password. -
Put your BIOS files in the folder the settings name:
mkdir -p ~/beck/bios
-
See what BECK would do. This connects and reads, but changes nothing:
beck check --dry-run
-
Do it:
beck check -
On your Recalbox, scan the BIOS files again, to see the result.
Safety
- Nothing is deleted unless you ask. BECK copies your files and leaves them where they were. Only
--moveand--clean-unmatcheddelete anything, and they ask first. Read what they delete before you use them:--clean-unmatchedcan delete good files. - Nothing on your Recalbox is replaced unless you ask. A file already there is kept and reported, unless you add
--overwrite. - Your password stays out of files. BECK asks for it, or reads it from
BECK_SMB_PASSWORD. It can't go in the settings file. - SMB isn't encrypted, so use BECK on a network you trust. The threat model says what BECK protects, and what it doesn't.
Configuration
Flags beat environment variables, which beat the settings file. The guide to the beck command has every setting and every option.
Automation and AI agents
Add --json to any command to get one JSON document on stdout, and branch on the exit code. --json never asks a question. To have an AI agent do this for you, see Using BECK with an agent. For AI
agents, AGENTS.md has the rules for using BECK safely.
Troubleshooting
BECK says what went wrong, and its exit code says what kind of problem it is. The troubleshooting guide goes through each message, with why it happens and what to do.
The most common one is that your computer can't find recalbox.local: use your Recalbox's IP address in url instead.
Project status
BECK is stable since 1.0: a change that could break how you use it, such as a command, a flag, an exit code or the --json output, waits for a new major version. It's been tested on Recalbox 10.1.1 in a virtual machine, but not yet on real hardware. Its automatic tests run on Linux only, so Windows and macOS
are untested. The changelog lists what has changed.
If you used an older copy, note that BECK no longer deletes every file it copies, and no longer reads config/config.yml. Since 1.0, check_bios.py is gone, and so is
running beck with no command: install BECK as above, and run beck check. If you still have that file, BECK prints what to put in
the new settings. Delete it afterwards, because it may hold your password in plain text. Older copies tracked it in git, so if you edited it, git pull refuses to update until
you move it out of the way.
Contributing
Help is welcome: the contributing guide says how to set up, what to work on, how to send a change, and how to share a report safely.
AGENTS.md has the commands and rules for working on BECK, for people and for AI agents. The roadmap is the plan, and
the design explains how it fits together.
Security
To report a problem, see the security policy.
License
GPL-3.0-only. See LICENSE.
Metadata
Release files for beck-bios 1.0.1
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 |
|---|---|---|---|---|
| beck_bios-1.0.1.tar.gz | 58.2 kB | With provenance | Details for beck_bios-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| beck_bios-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for beck_bios-1.0.1-py3-none-any.whl |
Total release size: 123.7 kB
Release files / beck_bios-1.0.1.tar.gz
| Download URL | beck_bios-1.0.1.tar.gz |
|---|---|
| Size | 58.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e54f08daedd8ddbcc4ad79c2cd531a9f13a13247810bcb0b2f15eec7d25b948
|
|
BLAKE2b-256 checksum How to use checksums |
17fd7ba579fbadb80440e1e98af4f444d4af771321b8eb311d7564301ba36cfa
|
| 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 11, 2026.
Transparency logRelease files / beck_bios-1.0.1-py3-none-any.whl
| Download URL | beck_bios-1.0.1-py3-none-any.whl |
|---|---|
| Size | 65.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9851a46a91b197db8cea910178e7235005459c210a5fbc72eefa1f5105d75e38
|
|
BLAKE2b-256 checksum How to use checksums |
8ab955e34177feb618f4569ec960628a20ab6f6906e653d5a18f0b133e05d1c7
|
| 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 11, 2026.
Transparency logSecurity for beck-bios 1.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
Both files in this release have been uploaded with provenance metadata.
Attestation for beck_bios-1.0.1.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 11, 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.