bodnuti

Deterministic checks of Yocto Project & OpenEmbedded patches.

bodnuti watches the Yocto Project and OpenEmbedded mailing lists, checks each patch series as it arrives with the tools the projects already use, and publishes what each series adds: the reports. It is in the spirit of sashiko.dev for the Linux kernel, but without a language model: every finding comes from a checker, compared before and after the series.

Sashiko (刺し子) means “little stabs”: the Japanese craft of reinforcing indigo cloth with small white running stitches. In Czech, that is malé bodnutí. Many small stitches, one patch at a time.

This week

What is checked

• Layers (OE-Core, meta-openembedded, BitBake, meta-virtualization, meta-security and more): patchtest, oelint-adv, shellcheck, and patch files left behind.
• Documentation (yocto-docs, the BitBake manual): the Sphinx build with warnings as errors, sphinx-lint, check-glossaries and check-confusables.
• Django applications (layerindex-web, error-report-web): patchtest's mail checks, ruff, djLint, and known vulnerabilities in the requirements pins a series changes.
• Python tools (the autobuilder, auto-upgrade-helper): patchtest's mail checks, ruff, shellcheck, and JSON that must still parse.
• C (pseudo): patchtest's mail checks, shellcheck and cppcheck.

Checks run offline in a read-only container. A series already merged, a resend, and where each patch landed upstream are recognised and shown.

Lists

• openembedded-core
• openembedded-devel
• bitbake-devel
• yocto-docs
• yocto-meta-virtualization
• yocto-patches

Project

• Source on GitHub (MIT or Apache-2.0), releases, reporting a vulnerability
• Sponsor the work
• Yocto Project contributor guide