What changed, and why it matters
This commit simply adds another supported hardware device name to a build/flash helper script. It does not change any cryptographic, wallet, or security-sensitive code. There is no indication of a vulnerability or security fix.
No security action required. Treat as routine device-support expansion.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch extends the ‘krux’ shell script to recognize ‘maixpy_yahboom_devkit’ as a valid device for both the ‘build’ and ‘flash/boot/erase’ commands. It adds two identical string comparisons to existing OR-chained device checks. The new device uses the same USB vendor/product ID mapping as other Yahboom-compatible boards. No logic, permissions, or trust boundaries are altered.
Changed components
krux build/flash helper scriptInspect captured patch +2 / −0
diff --git a/krux b/krux
index 2b4ac87..b01f3ff 100755
--- a/krux
+++ b/krux
@@ -67,6 +67,7 @@ if [ "$1" == "build" ]; then
[ "$device" == "maixpy_yahboom" ]||
[ "$device" == "maixpy_cube" ]||
[ "$device" == "maixpy_wonder_mv" ]||
+ [ "$device" == "maixpy_yahboom_devkit" ]||
[ "$device" == "maixpy_tzt" ]||
[ "$device" == "maixpy_wonder_k" ]||
[ "$allow_unsupported" ]; then
@@ -114,6 +115,7 @@ elif [ "$1" == "flash" -o "$1" == "boot" -o "$1" == "erase" ]; then
elif [ "$device" == "maixpy_dock" ]||
[ "$device" == "maixpy_yahboom" ]||
[ "$device" == "maixpy_wonder_mv" ]||
+ [ "$device" == "maixpy_yahboom_devkit" ]||
[ "$device" == "maixpy_wonder_k" ]; then
# https://devicehunt.com/view/type/usb/vendor/1a86/device/7523
device_vendor_product_id="1a86:7523"
Why this scored 16/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.