@goodandready/dsh-cron@0.3.18
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 manifest has no install hook, and the flagged client locations handle panel state and UI updates. Inspected credential use is tied to configured Telegram delivery; the scanner’s credential-exfiltration label is not supported by the source reviewed.
Decision evidence
public snapshot- package.json exposes the library entry point and has no install lifecycle hook.
- The flagged client code observes UI changes and subscribes to panel state; it does not transfer credentials.
- Croner is declared as the runtime dependency and its inspected entry point contains date and time calculations.
- The plugin patch registers this package with empty configuration.
- Telegram messages send the configured bot token to Telegram’s Bot API; the inspected client saves settings to the package’s local API.
- The package supports user-configured HTTP tasks and notification credentials, which are network capabilities but do not establish an attack.
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.18.
See all versions of @goodandready/dsh-cron for other recorded verdicts.
- Review the evidence and your use of @goodandready/dsh-cron@0.3.18 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.