Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

Perform a check to see if WinGet is installed and ignore it if it's not - or send a message back to say WinGet wasn't found..
Output a message for any system that is checked, but has no update, i.e. "Checked Chocolately and no updates are available".

Perform a check to see if WinGet is installed and ignore it if it's not - or send a message back to say WinGet wasn't found..
Output a message for any system that is checked, but has no update, i.e. "Checked Chocolately and no updates are available".

Think the latest commit addresses these points.

Takes a bit of time to run with no info coming back, so I'd put in some outputs like 'Checking Chocolatey...", etc.
Problem with your PS section as it creates the check file even if $ModuleUpdates is empty. You need to change:
$ModuleUpdates | ConvertTo-Json | Out-File -FilePath "$env:temp\powershell-outdated.json" -Encoding utf8 -Force
to
if ($ModuleUpdates) {
$ModuleUpdates | ConvertTo-Json | Out-File -FilePath "$env:temp\powershell-outdated.json" -Encoding utf8 -Force
}
You might also consider removing the output files after the script does its work to make sure subsequent runs don't pick them up.

Takes a bit of time to run with no info coming back, so I'd put in some outputs like 'Checking Chocolatey...", etc.
Problem with your PS section as it creates the check file even if $ModuleUpdates is empty. You need to change:
$ModuleUpdates | ConvertTo-Json | Out-File -FilePath "$env:temp\powershell-outdated.json" -Encoding utf8 -Force
to
if ($ModuleUpdates) {
$ModuleUpdates | ConvertTo-Json | Out-File -FilePath "$env:temp\powershell-outdated.json" -Encoding utf8 -Force
}
You might also consider removing the output files after the script does its work to make sure subsequent runs don't pick them up.

Hmmm, that's intended, I primarily use this to write the files in the temp folder, so I can read them when starting a new console, This is done to give you instant results on launching a new terminal window.
The output from the function is really only there in case it is run manually, but for the most part, I see this running on a scheduled task automatically.

That's fine, but you probably still don't want it creating empty files. Or if you do, there's no point in checking for the file and then outputting that there are no updates based on whether there's a file there or not.

Yeah fair point, I'll update to remove the files before it starts, then check the non-existence as a sign of no updates.

Looks good to me!