ddotisacat/scheduled-job-graveyardv0.1.3Public
Scheduled job graveyard
Reports the scheduled jobs on THIS machine you have probably forgotten exist: your user crontab (crontab -l), your ~/Library/LaunchAgents plists (parsed via plutil -convert json, degrading per-file on a bad plist), launchd own live status for those LaunchAgents (launchctl list -- pid and last-exit code), and -- names
Read the full description
only, content never opened, no sudo -- /etc/crontab, /etc/cron.d, and the system LaunchDaemons directories: five sources in all. On Linux the same crontab is read and systemd user timers (systemctl --user list-timers, plus each activated units own ExecStart line) stand in for LaunchAgents; every source degrades on its own rather than failing the whole play, and an absent source (no crontab, no LaunchAgents dir) is reported as a plain, honest absence, never a warning. Each user-owned job is classified as healthy, target-missing (the first absolute-path token found in its command no longer exists on disk), stale-suspect (that target mtime is older than stale_days with no recent-run evidence -- a li
Before you run it5 local tools
Everything here is checked on your machine when rote inspects the play. This page never learns what you have installed or which credentials you hold.
- ○python3local tool
Must be on your PATH when used. minimum version undeclared.
- ○plutillocal tooloptional
Must be on your PATH when used. minimum version undeclared.
- ○crontablocal tooloptional
Must be on your PATH when used. minimum version undeclared.
- ○launchctllocal tooloptional
Must be on your PATH when used. minimum version undeclared.
- ○systemctllocal tooloptional
Must be on your PATH when used. minimum version undeclared.
Inputs1, all optional
rote asks for these before running and shows the defaults it will use.
- Stale days
stale_daysA target script untouched this long is flagged stale-suspect (30-3650)
optionalintegerdefault365example365custom value allowed
What it changes
No write operations are declared in this version's manifest.
Credentials remain in the recipient's local rote vault; this page and the publisher never receive them.
Runtime details
- rote CLIversion 0.62.0 or newer
- Servicesnone declared
- Digest
sha256:a93bf1495c1a501945564f332917ee14def6648bec6fb0488c5b92d6d50a520a - Archive size22788 bytes
- Published2026-09-03T21:50:40.726852+00:00
- Published withrote 0.77.0
Credential values and current readiness remain local. Opening this page never prompts for a credential, opens an authorization browser, or calls a service this play uses.
A play is a published, versioned automation package that runs on your own machine through rote, a free command-line tool. Opening this page installs nothing and runs nothing.