crypto-hash-digest
Pass
Audited by Gen Agent Trust Hub on Aug 18, 2026
Risk Level: SAFECREDENTIALS_UNSAFEEXTERNAL_DOWNLOADSCOMMAND_EXECUTIONREMOTE_CODE_EXECUTIONPROMPT_INJECTION
Full Analysis
- [CREDENTIALS_UNSAFE]: The documentation instructs users to provide a cryptographic private key via the
FITTINGS_PRIVATE_KEYenvironment variable. Storing raw private keys in environment variables or shell history is a standard security risk, although the script uses this key only for local signing via theviemlibrary. - [EXTERNAL_DOWNLOADS]: The skill documentation suggests fetching the necessary helper script
call.mjsdirectly from the vendor's domain athttps://fittings.sh/skill/call.mjsusingcurlif it is missing. - [COMMAND_EXECUTION]: The skill execution relies on
node call.mjs, which performs network operations, accesses sensitive environment variables, and reads its own file content from the disk to perform a self-integrity check against a remote SHA-256 hash. - [REMOTE_CODE_EXECUTION]: The
call.mjsscript performs dynamic loading of Node.js modules (such as@x402/fetch,@x402/evm, andviem) at runtime using dynamicimport()statements. - [PROMPT_INJECTION]: The skill possesses an indirect prompt injection surface as it ingests untrusted input through the
textparameter. This data is transmitted to the remote API without sanitization. Evidence: - Ingestion points:
textparameter inSKILL.mdandcall.mjsCLI arguments. - Boundary markers: None present; text is passed directly into the JSON request body.
- Capability inventory: Network POST requests via
fetchtofittings.sh. - Sanitization: None; input is stringified directly into the request payload.
Audit Metadata