@goodandready/dsh-cron@0.3.28
Background automation runner for DSH: isolated agent runs, script/HTTP/SSH/Docker runtimes, cost guard, notifications, heartbeats.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged SSH-key and Feishu references are for user-configured task and notification settings. The Gitea token flow is gated by an opt-in setting and a model-produced action directive, and sends to a local Gitea API; no malicious behavior was identified.
Decision evidence
public snapshot- The package describes itself as a DSH automation runner with script, HTTP, SSH and Docker runtimes.
- LLM actions are disabled by default and execute only when enabled in settings after a successful LLM task produces output.
- The Gitea issue action reads a token and posts to a local Gitea API; it is reachable through the opt-in LLM action flow.
- The SSH-key pointer is a user-entered key-path field for an SSH task.
- The Feishu host appears as a configurable webhook destination in notification settings.
- When LLM actions are enabled, an LLM directive can create an issue in the default goodandready/dsh-cron repository using a token from the environment or a configured credentials file.
Source & flagged code
5 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
lib/tui-settings.jsView on unpkg · L68Source appears to send environment or credential material to an external endpoint.
Findings
Affected versions and remediation
This report applies to @goodandready/dsh-cron@0.3.28.
See all versions of @goodandready/dsh-cron for other recorded verdicts.
- Review the evidence and your use of @goodandready/dsh-cron@0.3.28 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.