@goodandready/dsh-cron@0.3.6
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 has no install lifecycle hook, and the credential-related client flow inspected posts a user-entered token to the package’s same-origin settings endpoint. The scanner’s credential-exfiltration hint is not supported by the inspected source.
Decision evidence
public snapshot- package.json declares lib/index.js as the entrypoint and lists no install lifecycle hook.
- lib/client.js sends the bot token to the package’s same-origin /dsh-cron/settings endpoint when settings are saved.
- lib/client.js runtime locations mount and clean up the interface; they do not show credential export.
- cordis.patch.yml registers dsh-cron with empty configuration.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
lib/client.jsView on unpkg · L127Findings
Affected versions and remediation
This report applies to @goodandready/dsh-cron@0.3.6.
See all versions of @goodandready/dsh-cron for other recorded verdicts.
- Review the evidence and your use of @goodandready/dsh-cron@0.3.6 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.