===========================================================
                                      .___ __  __   
          _________________  __ __  __| _/|__|/  |_ 
         / ___\_` __ \__  \ |  |  \/ __ | | \\_  __\
        / /_/  >  | \// __ \|  |  / /_/ | |  ||  |  
        \___  /|__|  (____  /____/\____ | |__||__|  
       /_____/            \/           \/           
              grep rough audit - static analysis tool
                  v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
ruby-sshkit-1.20.0/CHANGELOG.md-276-    @robd
ruby-sshkit-1.20.0/CHANGELOG.md:277:    * Use `SSHKit.config.output = SSHKit::Formatter::SimpleText.new($stdin)` instead
ruby-sshkit-1.20.0/CHANGELOG.md-278-  * Added support for `:interaction_handler` option on commands.
##############################################
ruby-sshkit-1.20.0/README.md-202-A problem often arises when calling out to executables expected to be on
ruby-sshkit-1.20.0/README.md:203:the `$PATH`.  Under conditions without dotfiles or other environmental
ruby-sshkit-1.20.0/README.md:204:configuration, `$PATH` may not be set as expected, and thus executables are not found where expected.
ruby-sshkit-1.20.0/README.md-205-
##############################################
ruby-sshkit-1.20.0/README.md-439-
ruby-sshkit-1.20.0/README.md:440:By default, formatters log to `$stdout`, but they can be constructed with any object which implements `<<`
ruby-sshkit-1.20.0/README.md-441-for example any `IO` subclass, `String`, `Logger` etc: