mcuboot-integration — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited mcuboot-integration (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill to integrate MCUboot by proving the boot chain, flash map, image format, signing flow, and upgrade policy. Most failures come from slot geometry, trailer layout, or signing metadata mismatches rather than the application itself.
Use this skill when:
Do not use this skill for application-level firmware transfer alone. Use ota-update-integration first if the bootloader is already fixed and the issue is delivery. For generic bootloader jump/handoff debugging, use bootloader-debug.
Ask for:
Slot sizes, erase block size, alignment, scratch size, and trailer offsets must match the target flash.
Verify image header, TLVs, signature, version, and load address before enabling OTA.
Boot one known-good image from the primary slot and record bootloader logs.
Test pending, test, confirm, revert, and permanent upgrade paths for the selected mode.
Keep serial recovery, debug access, watchdog policy, and factory image strategy clear.
Enable key protection, rollback counters, encryption, or anti-tamper only after the basic upgrade loop is repeatable.
Before claiming MCUboot works:
User:
MCUboot 升级后总是回滚。Agent:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.