Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand



Downloads of v


Last Update:

06 Jun 2024

Package Maintainer(s):

Software Author(s):

  • Simon Bennetts


zap admin dast security proxy attack web pentesting

Zed Attack Proxy (ZAP) (Install)

  • 1
  • 2
  • 3 | Updated: 06 Jun 2024



Downloads of v



Software Author(s):

  • Simon Bennetts

Zed Attack Proxy (ZAP) (Install)

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Exemption:

Dependency cannot be packaged on the Community Repository due licensing issues. See package description for more information.


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Zed Attack Proxy (ZAP) (Install), run the following command from the command line or from PowerShell:


To upgrade Zed Attack Proxy (ZAP) (Install), run the following command from the command line or from PowerShell:


To uninstall Zed Attack Proxy (ZAP) (Install), 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

  • 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 zap -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 zap -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 zap
    name: zap
    version: ''
    state: present

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

chocolatey_package 'zap' do
  action    :install
  source   'INTERNAL REPO URL'
  version  ''

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

cChocoPackageInstaller zap
    Name     = "zap"
    Version  = ""
    Source   = "INTERNAL REPO URL"

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

package { 'zap':
  ensure   => '',
  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.

Package Approved

This package was approved as a trusted package on 06 Jun 2024.


Zed Attack Proxy (ZAP)

The Zed Attack Proxy (ZAP) is one of the world’s most popular free security tools and is actively maintained by hundreds of international volunteers. It can help you automatically find security vulnerabilities in your web applications while you are developing and testing your applications. Its also a great tool for experienced pentesters to use for manual security testing.


Some of ZAP's functionality:

  • Intercepting Proxy
  • Traditional and AJAX spiders
  • Automated scanner
  • Passive scanner
  • Forced browsing
  • Fuzzer
  • Dynamic SSL certificates
  • Smartcard and Client Digital Certificates support
  • Web sockets support
  • Support for a wide range of scripting languages
  • Plug-n-Hack support
  • Authentication and session support
  • Powerful REST based API
  • Automatic updating option
  • Integrated and growing marketplace of add-ons

Package Note

ZAP 2.15 requires Java 11 or higher and that the JAVA_HOME environment variable is set. You can install a Chocolatey Java Package or Java from Oracle. One suggestion is the Temurin11jre package. Ensure you install it with the FeatureJavaHome parameter set.

Maintainer's Note

I produce and maintain Chocolatey packages in my spare time, for free. If you use my packages, and appreciate the time and effort I put into making and maintaining them, please consider making a small donation. Thank-you!

$ErrorActionPreference = 'Stop';

$packageName    = 'zap'
$toolsDir       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url32          = 'https://github.com/zaproxy/zaproxy/releases/download/v2.15.0/ZAP_2_15_0_windows-x32.exe'
$url64          = 'https://github.com/zaproxy/zaproxy/releases/download/v2.15.0/ZAP_2_15_0_windows.exe'
$checksum32     = '114953f29647a5e4e5774b338f2271d6149711e9222e0b92b11be3a35b812478'
$checksum64     = '28b348dd65116ddabbbbd98b7f84864a0bb0f98d656266f2f08bfd010ae51c57'
$pf             = ''

$packageArgs = @{
  packageName    = $packageName
  unzipLocation  = $toolsDir
  fileType       = 'EXE'
  url            = $url32
  url64bit       = $url64
  softwareName   = 'Zed Attack Proxy*'
  checksum       = $checksum32
  checksumType   = 'sha256'
  checksum64     = $checksum64
  checksumType64 = 'sha256'
  silentArgs     = '-q'
  validExitCodes = @(0)

$envJavaHome = $env:JAVA_HOME

# Detect JAVA_HOME in the calling user's environment, not the environment of the C4B chocolatey agent service account (by default ChocolateyLocalAdmin)
# Note: This must be in the registry. Setting $env:JAVA_HOME at the command line before calling choco install will *not* work.
if ($env:USER_CONTEXT) {
  $userObject = New-Object System.Security.Principal.NTAccount("", $env:USER_CONTEXT)
  $Sid = $userObject.Translate([System.Security.Principal.SecurityIdentifier])
  Write-Debug "User: '$($env:USER_CONTEXT)', SID: '$($Sid.Value)'"

  $userEnv = Get-ItemProperty "Registry::HKEY_USERS\$($Sid.Value)\Environment"
  $envJavaHome = $userEnv | Select-Object -ExpandProperty "JAVA_HOME" -ErrorAction "SilentlyContinue"
  Write-Debug "JAVA_HOME=$envJavaHome"

if (Test-Path $envJavaHome) {
  Write-Host "Java installed and JAVA_HOME set to '$envJavaHome'"
  $javaExe = Join-Path $envJavaHome "bin\java"
  $java_major_version = (Get-Command $javaExe | Select-Object -ExpandProperty Version).Major
  Write-Host "Java major version is: $java_major_version"
  if ( $java_major_version -ge 11 ) {
    Install-ChocolateyPackage @packageArgs
    if ( Get-OSArchitectureWidth 32 ) { $pf = ' (x86)' }
    Install-ChocolateyShortcut `
      -ShortcutFilePath "C:\Users\Public\Desktop\ZAP $($env:ChocolateyPackageVersion.SubString(0,6)).lnk" `
      -TargetPath "C:\Program Files$pf\ZAP\Zed Attack Proxy\ZAP.bat" `
      -WorkingDirectory "C:\Program Files$pf\ZAP\Zed Attack Proxy"
  } else {
    Write-Error "Java version is less than 11. ZAP 2.15 or greater requires Java 11."
} else {
  Write-Error "JAVA_HOME isn't set. Ensure you set this environment variable to a Java 11+ installation."
$ErrorActionPreference = 'Stop';

$packageName = 'zap'
$softwareName = 'Zed Attack Proxy*'
$installerType = 'EXE' 
$silentArgs = '-q'
$validExitCodes = @(0)

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $softwareName

if ($key.Count -eq 1) {
  $key | % { 
    $file = "$($_.UninstallString)"

    Uninstall-ChocolateyPackage -PackageName $packageName `
                                -FileType $installerType `
                                -SilentArgs "$silentArgs" `
                                -ValidExitCodes $validExitCodes `
                                -File "$file"
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$key.Count matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $_.DisplayName"}

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
Zed Attack Proxy (ZAP) (Install) 2.15.0 1064 Thursday, May 9, 2024 Approved
Zed Attack Proxy (ZAP) (Install) 2.14.0 6247 Saturday, October 14, 2023 Approved
OWASP Zed Attack Proxy (ZAP) (Install) 15336 Sunday, November 27, 2022 Approved
OWASP Zed Attack Proxy (ZAP) (Install) 152 Saturday, November 26, 2022 Approved
OWASP Zed Attack Proxy (ZAP) (Install) 2.12.0 1613 Thursday, October 27, 2022 Approved
OWASP Zed Attack Proxy (ZAP) (Install) 2.11.1 11229 Saturday, December 11, 2021 Approved
OWASP Zed Attack Proxy (ZAP) (Install) 2.11.0 8865 Friday, October 8, 2021 Approved
OWASP Zed Attack Proxy (ZAP) (Install) 2.10.0 11610 Thursday, December 17, 2020 Approved
OWASP Zed Attack Proxy (ZAP) (Install) 2.9.0 15777 Friday, January 17, 2020 Approved
OWASP Zed Attack Proxy (ZAP) (Install) 2.8.0 11736 Monday, June 10, 2019 Approved
OWASP Zed Attack Proxy (ZAP) (Install) 11991 Friday, December 8, 2017 Approved
OWASP Zed Attack Proxy (ZAP) (Install) 2.7.0 603 Wednesday, November 29, 2017 Approved
OWASP Zed Attack Proxy (ZAP) (Install) 2.6.0 919 Wednesday, March 29, 2017 Approved
OWASP Zed Attack Proxy (ZAP) (Install) 2.5.0 710 Friday, October 28, 2016 Approved

This package has no dependencies.

Discussion for the Zed Attack Proxy (ZAP) (Install) Package

Ground Rules:

  • This discussion is only about Zed Attack Proxy (ZAP) (Install) and the Zed Attack Proxy (ZAP) (Install) 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 Zed Attack Proxy (ZAP) (Install), 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