@goodandready/dsh-cron@0.3.17
Background automation runner for DSH: isolated agent runs, script/HTTP/SSH/Docker runtimes, cost guard, notifications, heartbeats.
AI Security Review
scanned 15d ago · by lpm-firewall-aiDirect inspection did not substantiate the scanner's credential-exfiltration hint: the client submits the configured bot token to the package's relative settings endpoint, while the flagged runtime operations synchronize UI state. The manifest has no install lifecycle hook, and the inspected dependency and plugin patch show no concrete attack behavior.
Decision evidence
public snapshot- The manifest points to the plugin entrypoint and lists test and build scripts, with no install lifecycle hook.
- The settings form posts the entered bot token to the relative /dsh-cron/settings route when submitted.
- The flagged client runtime locations subscribe to and synchronize UI state.
- The heartbeat sends a GET only when a URL and positive interval are supplied through configuration.
- The declared croner dependency has no lifecycle scripts in its inspected manifest; its inspected source implements date and cron parsing.
- The patch registers the plugin with empty configuration.
- The scanner's credential-exfiltration hint is not supported by the inspected client: its credential-bearing request targets the package's relative settings route, and no external recipient was found there.
- The flagged runtime-operation locations concern UI toggle subscriptions, not credential transfer or account actions.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
lib/client.jsView on unpkg · L128Findings
Affected versions and remediation
This report applies to @goodandready/dsh-cron@0.3.17.
See all versions of @goodandready/dsh-cron for other recorded verdicts.
- Review the evidence and your use of @goodandready/dsh-cron@0.3.17 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.