@goodandready/dsh-cron@0.3.19
Background automation runner for DSH: isolated agent runs, script/HTTP/SSH/Docker runtimes, cost guard, notifications, heartbeats.
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe scanner’s client findings resolve to UI state handling, while the credential path is used for configured Telegram delivery. The manifest has no install lifecycle hook, and the inspected dependency source is consistent with cron scheduling.
Decision evidence
public snapshot- package.json points to lib/index.js and lib/client.js and declares no install lifecycle hook.
- lib/client.js subscribes to panel toggle state and mounts or removes UI elements at the inspected runtime locations.
- lib/secrets.js resolves configured credential references through the host credentials service; lib/index.js passes that resolver to the scheduler and delivery path.
- lib/telegram.js sends configured notification content to Telegram’s Bot API.
- The inspected croner manifest and source identify a cron scheduler dependency; its source excerpt shows date calculations.
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.19.
See all versions of @goodandready/dsh-cron for other recorded verdicts.
- Review the evidence and your use of @goodandready/dsh-cron@0.3.19 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.