potential ways to identify popular bash script-based tools

[wangmot]

Could be used for building an info extractor that tries to figure out what a bash script is. Mainly, it tries to answer this question:

What open-source software projects are developed primarily in Bash, and what specific characteristics or identifying features like naming conventions, function names, and comments could we look for to determine whether an arbitrary Bash script we come across comes from one of those open-source Bash projects?

1. NVM
   -look for its filepath: ~/.nvm/nvm.sh
   -open/read the file and look for function names like nvm_command_info() & nvm()
   -check for header comment stating Node Version Manager
   -other heuristics

2. Pyenv

• scripts: https://github.com/pyenv/pyenv/tree/master/libexec
  -libexec/pyenv is the main script that calls the subcommand scripts.
  -Look for variables like PYENV_ROOT, PYENV_DIR, PYENV_HOOK_PATH
  -function names like abs_dirname() & abort()

3. rbenv
   scripts: https://github.com/rbenv/rbenv/tree/master/libexec
   -Look for env variables & strings like RBENV_ROOT, RBENV_DIR, RBENV_HOOK_PATH, RBENV_ORIG_PATH, RBENV_DEBUG, rbenv---version

• function names: canonicalize(), abort()

4. RVM
   -scripts: https://github.com/rvm/rvm/tree/master/bin

• Look for variables like rvm_path, rvm_is_not_a_shell_function, & rvmrc

5. chruby
   Main script: https://github.com/postmodern/chruby/tree/master/share/chruby
   -look for string CHRUBY_VERSION="*" and function names chruby_reset(), chruby_use(), chruby()
   -env vars RUBY_ROOT, RUBY_ENGINE, RUBY_VERSION, RUBYOPT, GEM_ROOT

6. asdf
   -Look for ASDF_DIR, ASDF_DATA_DIR, ASDF_FORCE_PREPEND, _asdf_should_prepend, and function name asdf(), file name asdf.sh

7. GVM (go version manager)

• Main script: https://github.com/moovweb/gvm/tree/master/bin
  -Look for env variables & strings like GVM_ROOT, GVM_DEBUG, GVM_ROOT/scripts/gvm-check

8. sdkman

• Main script: https://github.com/sdkman/sdkman-cli/tree/master/src/main/bash
  -Look for env variables & strings like “# Copyright 2021 Marco Vermeulen”, SDKMAN_DIR, SDKMAN_PLATFORM, __sdkman_complete_candidate_version
  -Function names sdk(), ___sdkman_help(), __sdkman_complete_command()

9. nodenv
   -Main scripts: https://github.com/nodenv/nodenv/tree/main/libexec
   -Look for env variables & strings like NODENV_DEBUG, NODENV_ROOT, NODENV_DIR, NODENV_HOOK_PATH

• Function names: canonicalize(), abort()

10. jEnv
    -Main scripts: https://github.com/jenv/jenv/tree/master/libexec
    -Look for env variables & strings like JENV_DEBUG, JENV_ROOT, JENV_DIR
    -- Function names: _jenv(), abs_dirname(), resolvepath(), samedir()

[nightlark]

Another interesting class of shell scripts to identify: CMake-generated .sh installers, and potentially automate extraction of files in them without running the script