How it works
Whatever lands in the expression line is unwrapped before it is read: a leading #, a schedule: or cron: key with its YAML dash, quotes and a trailing comma. The rest is split on whitespace. @reboot is recognised on its own and the other nicknames are expanded to their five fields; otherwise tokens are counted while they look like fields — digits, * and ?, ranges, steps, month and weekday names — up to six. Five or more make a schedule and the remaining tokens are set aside as the command; fewer are a half-typed expression and stay in the boxes they belong to. Six fields switch the seconds column on.
Each field is split on commas, then on the dash and the slash. Names are accepted as JAN or January, in any case, but only as the three-letter form or the whole word. Day-of-week 7 is folded onto Sunday, 5/20 means from 5 to the end of the range in steps of 20, and a backwards range is refused with the split it has to be written as, because cron ranges never wrap. L, W and # are rejected as Quartz extensions. Whether both day columns are restricted is read from the text, as Vixie cron reads it: a field that starts with * or ? is unrestricted, and anything else makes the two columns an either/or.
The sentence is built from the expanded values: one minute and one hour read as a clock time, a few combinations are listed in full, and anything wider becomes clauses, with the day clauses joined by “or” when either column can fire the job and by “and” when both must hold. Next runs are found by stepping a calendar cursor forward from now, in your zone or in UTC, skipping months, days and hours that cannot match, for up to ten years; 30 February comes back empty and is reported as never running. The stats bar multiplies the second, minute and hour values together, then by the matching days in the next 365.