asus-esc8000-firmware-upgrade — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited asus-esc8000-firmware-upgrade (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.
Validated end-to-end on ESC8000-E12P (ASMB12-iKVM, AMI SP-X gen13). BMC updates are host-safe; BIOS updates require the chassis powered OFF and a host reboot.
export BMC_PASSWORD='...'
scripts/check_versions.sh <BMC_IP> # current BMC FW, BIOS, power state
scripts/check_versions.sh <BMC_IP> ESC8000-E12P # + latest versions from ASUS APIDownload zips from the URLs the ASUS API returns. BIOS zip → .HPM (BMC-flashable) + .CAP (EzFlash only — don't use here). BMC zip → .hpm.
scripts/bmc_update.sh <BMC_IP> <BMC_fw.hpm>Does: preserve-config flags → Redfish multipart push → flash → BMC auto-reboot → version verify. ~10 min. Warning: after the BMC reboots, the host may power ON via power-restore policy — re-check chassis state before any subsequent BIOS work.
POST /redfish/v1/Systems/<id>/Actions/ComputerSystem.Reset {"ResetType":"GracefulShutdown"} and wait for PowerState: Off.
python3 scripts/bios_update.py --ip <BMC_IP> --file <BIOS.HPM>{"ResetType":"On"}. First POST takes 5–15 min (memory retraining).BiosVersion in Redfish flips mid-POST; then verify the OS comes back.
Update BMC first, then BIOS (paired releases). Do not run two flashes concurrently.
Symptoms: web UI loads but login returns {"error":"Could not login","code":1348} ("Firmware update in progress hence login has been blocked"), Redfish 503, SSH/IPMI/KVM ports closed. No remote fix exists once all sessions are gone — it never times out.
→ AC drain: unplug both PSU cords (or PDU outlets) 30 s, replug. BMC boots clean in ~3 min. Prevention: never abandon the firmware wizard mid-flow; the scripts here always exit update mode on failure, and hpm/exitupdatemode {"FWUPDATEID":N} works from ANY admin session.
Managers/Self & Systems/Self are invalid — discover members (Managers/BMC_0, Systems/System_0).ForceRestart; reset bounces the host ON via power-restore policy.OemParameters={"ImageType":"HPM"}.UpdateService/upload path CANNOT flash BIOS (demands an unsatisfiableBiosUpdateMethod) — use the HPM wizard API (Workflow B).
PUT hpm/flash — without it the flash never startsand upgradestatus returns 500 code 1442 "Error in HPM Finish Firmware Upload".
ipmitool hpm upgrade does not work: 0xD5 refusal, and ~3 KB/s if it runs at all.See REFERENCE.md for the complete API map, payloads, and error-code table.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.