endianness-and-byte-order

Pass

Audited by Gen Agent Trust Hub on Oct 3, 2026

Risk Level: SAFE
Full Analysis
  • [SAFE]: The skill is entirely focused on educating users about C programming best practices related to byte order and endianness. It correctly identifies and explains significant security risks in C such as undefined behavior (UB) from type punning, alignment hazards, and non-portable serialization.
  • [SAFE]: The included utility examples/tools/endian_check.py is a benign static analysis tool that uses regular expressions to flag potential issues in C source code. It operates locally on provided file paths and does not perform any network operations or dangerous command execution.
  • [SAFE]: The skill provides both 'good' examples (portable, shift-based serialization) and 'bad' examples (native struct fwrite, union punning) which are clearly labeled for educational purposes. This separation helps prevent accidental misuse of insecure patterns.
  • [SAFE]: All external references provided in references/endianness.md (such as man pages, RFCs, and Wikipedia) are well-known, trusted documentation sources and are presented in plain text.
  • [SAFE]: No evidence of prompt injection, data exfiltration, obfuscation, or persistence mechanisms was found across the 11 files analyzed. The skill follows standard C11 (N1570) guidelines and industry best practices for network programming.
Audit Metadata
Risk Level
SAFE
Analyzed
Oct 3, 2026, 10:21 PM