Downloads:
45,036
Downloads of v 2.0.0:
4,632
Last Update:
20 Mar 2021
Package Maintainer(s):
Software Author(s):
- Kied Llaentenn
- contributors
Tags:
winfetch neofetch commandline systeminfo screenshot- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
winfetch
This is not the latest version of winfetch available.
- 1
- 2
- 3
2.0.0 | Updated: 20 Mar 2021
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
45,036
Downloads of v 2.0.0:
4,632
Maintainer(s):
Software Author(s):
- Kied Llaentenn
- contributors
winfetch 2.0.0
This is not the latest version of winfetch available.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install winfetch, run the following command from the command line or from PowerShell:
To upgrade winfetch, run the following command from the command line or from PowerShell:
To uninstall winfetch, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download winfetch --internalize --version=2.0.0 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade winfetch -y --source="'INTERNAL REPO URL'" --version="'2.0.0'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade winfetch -y --source="'INTERNAL REPO URL'" --version="'2.0.0'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install winfetch
win_chocolatey:
name: winfetch
version: '2.0.0'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'winfetch' do
action :install
source 'INTERNAL REPO URL'
version '2.0.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller winfetch
{
Name = "winfetch"
Version = "2.0.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'winfetch':
ensure => '2.0.0',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved by moderator virtualex on 21 Mar 2021.
NOTE: The following text is an excerpt from the official README.md.
Winfetch is a command-line system information utility written in PowerShell 5+. Winfetch displays information about your operating system, software and hardware in an aesthetic and visually pleasing way.
The overall purpose of Winfetch is to be used in screenshots of your system. Winfetch shows the information other people want to see. There are other tools available for proper system statistic/diagnostics.
The information by default is displayed alongside your operating system's logo. You can further configure Winfetch to instead use an image, your wallpaper or nothing at all.
According to benchmarks done with Hyperfine, Winfetch on Windows is faster than Neofetch running on Bash emulators like MSYS (Git Bash) or Cygwin.
$ErrorActionPreference = 'Stop';
$version = '2.0.0'
$packageArgs = @{
packageName = $env:ChocolateyPackageName
zipFileName = "winfetch-$version"
softwareName = 'winfetch*'
}
Remove-Item "$env:ChocolateyInstall\bin\winfetch.bat" -Force
Uninstall-ChocolateyZipPackage @packageArgs
Log in or click on link to see number of positives.
- winfetch.2.0.0.nupkg (629056bf3689) - ## / 61
- winfetch-2.0.0.zip (53eda3231f7a) - ## / 62
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
winfetch 2.5.1 | 8332 | Saturday, August 26, 2023 | Approved | |
winfetch 2.5.0 | 7313 | Tuesday, January 31, 2023 | Approved | |
winfetch 2.4.1 | 7990 | Wednesday, May 4, 2022 | Approved | |
winfetch 2.4.0 | 543 | Saturday, April 30, 2022 | Approved | |
winfetch 2.3.0 | 6471 | Saturday, November 6, 2021 | Approved | |
winfetch 2.2.0 | 9659 | Monday, August 30, 2021 | Approved | |
winfetch 2.1.0 | 96 | Monday, August 30, 2021 | Approved | |
winfetch 2.0.0 | 4632 | Saturday, March 20, 2021 | Approved |
Copyright (c) 2019-2021 Kied Llaentenn and contributors
Fixed
- Fixed errors when using strict-mode
- Fixed errors when using
-noimage
- Fixed issues with image processing especially for larger images
- Fixed detailed help not showing
New Features
- Improved terminal detection
- Improved scoop pkgs speed
- Disable unused package managers, use
-showpkgs [enabled pkgs]
- Change the order of info segments
- Insert blank info lines
- Hide the colorbar
- Colorbar now shows 16 colors
- Add custom info segments in the config
- Info lines are now written out progressively
- Info segments can now display multiple lines
- Show info for multiple disks, use
-showdisks *
- Added legacy windows logo, use
-switchlogo
to use the alternate logo - Added
-all
parameter to show all built-in info segments (regardless of your config) - Added
-stripansi
parameter to disable colors/fancy formatting similar to--stdout
in neofetch - Added
-configpath
parameter andWINFETCH_CONFIG_PATH
environment variable to override the default location of the config - Command-line parameters will now override those set in the config
- Long lines will now be truncated instead of wrapping to the next line
- Added a basic legacy branch for systems older than Windows 7
- The default config is now embedded within winfetch.ps1 and is generated automatically if your config doesn't exist
- Added percentage bars to cpu, memory, disk and battery, they are configured similar to neofetch, for example, use
winfetch -cpustyle bar -diskstyle textbar
New Info
- kernel
- resolution
- motherboard
- battery
- local_ip
- public_ip
- cpu_usage
- locale
- theme
New Configuration
We have also switched to a much more modular approach for info segments, this simplified the code and made it easier to add new info segments. This change also allows users to add custom info segments in their config. The default config has been updated, see the configuration docs for more information.
If you never used winfetch -genconf
before then you should automatically be switched to the new config, otherwise, you can regenerate a new config with winfetch -genconf
.
Optionally, you can attempt to migrate your old configuration, this commit may help.
Benchmarks
There have been many improvements to speed since v1.2.0
. Comparing v1.2.0
to v2.0.0
with the same segments enabled 1500ms
-> 350ms
which is around a 4x
improvement. More details can be seen on the winfetch vs neofetch benchmarks.
This package has no dependencies.
Ground Rules:
- This discussion is only about winfetch and the winfetch package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or winfetch, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.