It passes the following code checkers:
It gives either CSV (pipe separated) or JSON as output, depending on comand line options. CSV is the default, but you can specify --as-json for JSON output.
It traverses endlessly under your focus prefixes, but will only go one link deep on URL's that don't match your focus prefixes.
Usage is like:
$ ./find-dead-links --help below cmd output started 2018 Tue Feb 06 10:49:53 AM PST Usage: ./find-dead-links --verbose --focus-prefix http://host/ --timeout seconds --as-json --urls url1 url2 ... urln --focus-prefix may be specified more than once. Default output format is 3-column csv. The first column is the kind of problem detected, the second is the link that had a problem, and the third column is the referrer link. Or you can specify --as-json, which is mostly self-explanatory.
Example use:
$ ./find-dead-links --as-json --focus-prefix http://stromberg.dnsalias.org/ --urls https://stromberg.dnsalias.org/~strombrg/spider-test/good-local-1.html below cmd output started 2018 Tue Feb 06 11:02:35 AM PST [ { "bad_link": "http://docs.sun.com/app/docs/coll/QFS_4.3", "problem": "dead", "referrer_link": "https://stromberg.dnsalias.org/~strombrg/spider-test/good-local-1.html" }, { "bad_link": "http://www.amazon.com", "problem": "dead", "referrer_link": "https://stromberg.dnsalias.org/~strombrg/spider-test/good-local-1.html" }, { "bad_link": "https://stromberg.dnsalias.org/~strombrg/spider-test/bad-local-1.html", "problem": "dead", "referrer_link": "https://stromberg.dnsalias.org/~strombrg/spider-test/good-local-2.html" } ]
Related work:
You can e-mail the author with questions or comments: