• 1
  • 2
  • 3

1.3.0 | Updated: 08 Feb 2018



Downloads of v 1.3.0:



Software Author(s):

  • Badgerati

  • 1
  • 2
  • 3
Fudge 1.3.0

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Fudge, run the following command from the command line or from PowerShell:


To upgrade Fudge, run the following command from the command line or from PowerShell:


To uninstall Fudge, run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: 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

  • 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

3. Copy Your Script

choco upgrade fudge -y --source="'INTERNAL REPO URL'" [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 fudge -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install fudge
    name: fudge
    version: '1.3.0'
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

chocolatey_package 'fudge' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.3.0'

See docs at https://docs.chef.io/resource_chocolatey_package.html.

cChocoPackageInstaller fudge
    Name     = "fudge"
    Version  = "1.3.0"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.

package { 'fudge':
  ensure   => '1.3.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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 11 Jul 2020.


Fudge is a PowerShell tool to help manage software packages via Chocolatey for specific development projects. Think NPM and Bower, but for Chocolatey.


  • Uses a Fudgefile to control required software
  • Allows you to version control required software to run websites, services and applications
  • Ability to run pre/post install/upgrade/downgrade/uninstall/pack scripts
  • Can seperate out developer specific software which aren't needed for certain environments
  • You can reinstall all packages, or just in/un/reinstall all packages
  • Allows you to have mutliple nuspecs, which you can then pack one or all of with Fudge
  • See details about packages in a Fudgefile - such as which ones are installed or need upgrading
  • Create empty template Fudgefiles, or create them from nuspec files
  • Prune the machine to remove packages not in a Fudgefile (except chocolatey/fudge obviously!)
  • Clean a machine of all packages installed (again, except chocolatey/fudge)

$ErrorActionPreference = 'Stop';

$packageName    = 'Fudge'
$toolsDir       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url            = 'https://github.com/Badgerati/Fudge/releases/download/v1.3.0/1.3.0-Binaries.zip'
$checksum       = '0DC579F290F98766A58CB83AF85EB5B9323275C8BE62966F03480231CCA48835'
$checksumType   = 'sha256'

$packageArgs = @{
  PackageName   = $packageName
  UnzipLocation = $toolsDir
  Url           = $url
  Checksum      = $checksum
  ChecksumType  = $checksumType

# Download
Install-ChocolateyZipPackage @packageArgs

# Install
Write-Host 'Updating environment Path'
$path = Join-Path $env:chocolateyPackageFolder 'tools/src'
Install-ChocolateyPath -PathToInstall $path -PathType 'Machine'
# Uninstall
function Remove-Fudge($path)
    $current = (Get-EnvironmentVariable -Name 'PATH' -Scope 'Machine')
    $current = $current.Replace($path, [string]::Empty)
    Set-EnvironmentVariable -Name 'PATH' -Value $current -Scope 'Machine'

$path = Join-Path $env:chocolateyPackageFolder 'tools/src'
$pathSemi = "$($path);"

Write-Host 'Removing Fudge from environment Path'
if (($env:Path.Contains($pathSemi)))
    Remove-Fudge $pathSemi
elseif (($env:Path.Contains($path)))
    Remove-Fudge $path

Log in or click on link to see number of positives.

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
Fudge 1.2.1 314 Thursday, January 18, 2018 Approved
Fudge 1.2.0 330 Monday, September 4, 2017 Approved
Fudge 1.1.0 321 Thursday, August 24, 2017 Approved
Fudge 1.0.0 346 Sunday, August 6, 2017 Approved

This package has no dependencies.

Discussion for the Fudge Package

Ground Rules:

  • This discussion is only about Fudge and the Fudge 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 Fudge, 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.
comments powered by Disqus