@goodandready/dsh-cron@0.3.34
Background automation runner for DSH: isolated agent runs, script/HTTP/SSH/Docker runtimes, cost guard, notifications, heartbeats.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe scanner’s SSH and Feishu indicators correspond to a user-entered SSH key path and a configurable notification webhook, not automatic key collection or exfiltration. The Gitea issue action is gated behind an LLM-actions setting that defaults to false and sends its credential to a local API endpoint.
Decision evidence
public snapshot- The package manifest has no install, preinstall or postinstall lifecycle script.
- LLM action directives run only after a successful LLM task and when the setting is enabled; that setting defaults to false.
- The issue-creation helper uses a Gitea token only for its local API endpoint at 127.0.0.1:3005.
- The SSH key path is a user-entered task field, and Feishu appears as a configurable notification webhook.
- When enabled, an LLM action can create an issue in the default repository goodandready/dsh-cron using a Gitea credential; this is a sensitive capability, but it is gated by the LLM-actions setting.
Source & flagged code
11 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.34.
See all versions of @goodandready/dsh-cron for other recorded verdicts.
- Review the evidence and your use of @goodandready/dsh-cron@0.3.34 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.