neofetch triggers additional Terminal permissions in macOS 10.15.7

[DavidLiedle]

Description

If you're suggesting a new feature then just a description will suffice.

• [ x] Does this issue still occur in the master branch? (Required if issue)

Yes and no - it happens in the default installation provided and updated by brew, a.k.a. Homebrew. I have not tested directly from the GitHub repo.

Neofetch version

[~]$ brew info neofetch                                                                                                                                                                                                                     rvm:ruby-2.7.1 
neofetch: stable 7.1.0 (bottled), HEAD
Fast, highly customisable system info script
https://github.com/dylanaraps/neofetch
/usr/local/Cellar/neofetch/7.1.0 (6 files, 351.5KB) *
  Poured from bottle on 2020-08-04 at 18:22:45
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/neofetch.rb
License: MIT
==> Dependencies
Required: imagemagick ✔, screenresolution ✔
==> Options
--HEAD
        Install HEAD version
==> Analytics
install: 6,033 (30 days), 22,663 (90 days), 72,093 (365 days)
install-on-request: 6,027 (30 days), 22,617 (90 days), 71,898 (365 days)
build-error: 0 (30 days)
[~]$

Screenshot

Output got as far as Shell: and Resolution: on the terminal, then.....boop!

I didn't allow it. It then continued output with Terminal: Apple_Terminal and carried on to complete the output:

Config file

~/.config/neofetch/config.config

Verbose log

1. Run neofetch -vv 2> neofetchlog
2. Upload the contents of neofetchlog to pastebin, gist or equivalent.

neofetch -vv 2> neofetchlog && cat neofetchlog | pbcopy

[dylanaraps]

It's most likely the osascript stuff from first glance. This could be one of the offending pieces of code:

        "Apple_Terminal")
            term_font="$(osascript <<END
                         tell application "Terminal" to font name of window frontmost
END
)"
        ;;

[strafe]

I haven't encountered this on macOS 11.0.1 so maybe Apple has altered the way automation permissions work (at least for Terminal.app or apps that want to control themselves).