webhelm

This is a local browser automation daemon with a Unix socket at ~/.config/browser-workspace/runtime/session.sock, normally accessible only to the owning user because the runtime directory is mode 0700 and the socket is mode 0600. Its exec operation intentionally executes client-supplied Python in the daemon process without sandboxing, so an authorized socket client can perform actions with the daemon user's privileges; this is a significant local trust-boundary risk, not evidence of malware. Request-provided URLs are also navigated by the browser. No suspicious domains, credential harvesting, or obfuscated code are present in the fragment.

This workflow tests and publishes a public npm package and reports the result. No direct malware or data theft is evident in the supplied YAML. The main security concern is that external actions are referenced by mutable refs and execute in a publishing job with `id-token: write`, creating a path for a compromised action to abuse npm trusted publishing; pin actions to verified commit SHAs and minimize permissions where practical. Overall severity is moderate due to publishing authority and third-party action trust.