On similarity to dbus-scripts I want to mention the following points:

+ the command can be not only single script name w/o spaces, it can be any
arbitrary string, include spaces and different shell-orientent
expressions etc.,
+ it can listen to both session & system buses at the same time (which is
critical to me),
+ it can (hopefully) run without run-standalone.sh,
+ it provides full DBUS message info to script in environment variables,
+ arguments are matched as strings, and they are converted to them in a
quite smart way, so you can match even bools ('1' for true and '0'),
arrays as '1,2,3' or dicts as 'a:1,b:2,c:3' (well, there's still small
bug in it I will target in closest release, but it's a really quick and
easy fix),
+ any scripts written for dbus-scripts, are already compatible with dbuscron,
just use "scriptname $DBUS_ARG0 $DBUS_ARG1 $DBUS_ARG2" as command in dbuscrontab,
or replace $1,$2,... in script with $DBUS_ARG0,$DBUS_ARG1,...,

- it doesn't match rules with fnmatch(), but with simple string comparison,
so no wildcards (except for '*', which is not wildcard exactly), but it
is in my todo list.