hermes-graphify-gsd-project-integration

SUSPICIOUS: the skill’s stated repo-integration purpose mostly matches its file edits and verification steps, but it also mandates global installation and upgrade of third-party tools with unpinned commands. The source/publisher relationship is weakly trusted, and the optional autonomous-continuation workflow expands scope beyond simple repo integration. No clear credential theft or malicious exfiltration is evident.

No explicit malicious actions (exfiltration, credential theft, reverse shells) are present in the provided snippet itself. However, the bootstrap is high-risk from a supply-chain perspective because it fetches and installs remote code using unpinned/upgradable mechanisms (`pip install -U ...`, npm `@latest`) and executes an npm package via `npx` with `--global`. Additionally, the apparent `graphifyy` naming inconsistency and PATH fallback for `graphify` could lead to installing/executing unintended packages/binaries. This should be reviewed and ideally replaced with pinned versions plus integrity verification and deterministic lockfiles before use in security-sensitive environments.

This module is a bootstrapper that performs multiple high-impact supply-chain operations: it installs a Python package via unpinned pip (-U graphifyy) and executes additional tooling via npx using an unpinned @latest npm package (get-shit-done-cc@latest). While the snippet itself contains no obvious direct malware actions, the moving-target remote execution paths introduce a significant risk that behavior can change over time or be compromised. It should be revised to use pinned versions and integrity/provenance checks (e.g., lockfiles, hashes, allowlisted registries) and to minimize execution of remote CLIs during unattended bootstrap.