@goodandready/dsh-cron@0.2.48
Background automation runner for DSH: isolated agent runs, script/HTTP/SSH/Docker runtimes, cost guard, notifications, heartbeats.
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest exposes the plugin entrypoint but defines no install lifecycle hook. Inspected client requests carry user-entered settings to local package routes, while the scanner’s runtime locations show DOM lifecycle cleanup rather than credential transfer.
Decision evidence
public snapshot- package.json exposes lib/index.js and has no install lifecycle hook.
- The flagged client runtime code installs a DOM observer and removes it during cleanup.
- The client submits settings and a manually requested Telegram test to same-origin /dsh-cron routes.
- cordis.patch.yml registers the plugin with empty configuration.
- The browser UI accepts the bot token through a password field and sends it to the package’s local routes.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
lib/client.jsView on unpkg · L176Findings
Affected versions and remediation
This report applies to @goodandready/dsh-cron@0.2.48.
See all versions of @goodandready/dsh-cron for other recorded verdicts.
- Review the evidence and your use of @goodandready/dsh-cron@0.2.48 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.