The reviewed findings are consistent with Werkmeister’s stated purpose: setup is an explicit workflow, Slack requests use the configured Slack token for a user-requested message, and the suspicious socket code belongs to a localhost fixture. The package declares no install lifecycle scripts.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Slack posting and machine setup require an explicit function or command invocation; fixture server starts only when its fixture helper is called.
Impact
No automatic credential theft, unrelated collection, or hidden persistence was found in the reviewed paths.
Mechanism
Slack credentials are sent to Slack’s API for the requested message. Setup configures the developer machine for Werkmeister, while the fixture HTTP server listens on localhost.
Evidence
package.jsondist/sandbox.jsdist/machine_setup.jsdist/fixture_fakes.js
Network endpoints2
slack.com/api/chat.postMessage127.0.0.1:<ephemeral-port>