SCAN's version history starts with 2.2.1 because, prior to this release, it was developed internally at Comcast.
Some known issues with this release:
* In an effort to negate any performance impact on running instances of Apache Traffic Server (ATS), `scan`'s ionice is currently set to the lowest possible value (IDLE) whenever a loadavg isn't specified. This can make it painfully slow.
* FIPS is not very well supported (read: "doesn't work")
* The `-d`/`--dump` option doesn't allow for specification of a configuration directory, and currently uses the Comcast-preferred default of `/opt/trafficserver/etc/trafficserver`. Dumps will fail if you have a more standard installation.
* Instead of reading possibly-configured values for the locations of other config files from `records.config`, SCAN currently tries to find them _only_ in the same directory in which `records.config` is located.
* URLs do not currently display query strings or parameters when printed, even if the information is available.
* Much of figuring out where a URL is located is currently guesswork, and needs to be improved.
* SCAN will ignore alternate sources when searching for URLs, favoring the first listed alternate.
* Some `Dirs` appear to point at "first `Doc`s", but actually point to a mere fragment of some other `Doc`, and the only way I know how to figure out if this is the case at this point is to pay the price of reading in the `Doc` structure and check the `hlen` value, which is extremely inefficient.