Downloads of v


Last Update:

21 May 2014

Package Maintainer(s):

Software Author(s):

  • JetBrains


php work IDE JetBrains

JetBrains PhpStorm

This is not the latest version of JetBrains PhpStorm available.

  • 1
  • 2
  • 3 | Updated: 21 May 2014



Downloads of v


Software Author(s):

  • JetBrains

  • 1
  • 2
  • 3
JetBrains PhpStorm

This is not the latest version of JetBrains PhpStorm available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Unknown

Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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


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


To uninstall JetBrains PhpStorm, 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

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 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 phpstorm -y --source="'INTERNAL REPO URL'" --version="''" [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 phpstorm -y --source="'INTERNAL REPO URL'" --version="''" 

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

Exit $exitCode

- name: Install phpstorm
    name: phpstorm
    version: ''
    state: present

See docs at

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

See docs at

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

Requires cChoco DSC Resource. See docs at

package { 'phpstorm':
  ensure   => '',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

There are versions of this package awaiting moderation . See the Version History section below.

This package was approved as a trusted package on 05 Apr 2017.


PhpStorm keeps up with latest PHP and web languages trends, integrates a variety of modern tools, and brings even more extensibility with support for major PHP frameworks.

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
JetBrains PHPStorm 2022.1-EAP221-3427-92 7 Friday, January 28, 2022 Exempted
JetBrains PHPStorm 2021.3.2-EAP213-6777-13 21 Tuesday, January 18, 2022 Approved
JetBrains PHPStorm 2021.3.1-EAP213-6461-28 25 Saturday, December 18, 2021 Approved
JetBrains PHPStorm 2021.3 572 Thursday, December 2, 2021 Approved
JetBrains PHPStorm 2021.3-EAP213-5744-38 33 Friday, November 12, 2021 Exempted
JetBrains PHPStorm 2021.3-EAP213-5605-81 28 Friday, November 5, 2021 Exempted
JetBrains PHPStorm 2021.3-EAP213-5449-28 23 Monday, November 1, 2021 Approved
JetBrains PHPStorm 2021.3-EAP213-5281-20 28 Saturday, October 23, 2021 Exempted
JetBrains PHPStorm 2021.3-EAP213-4928-13 31 Friday, October 15, 2021 Approved

This package has no dependencies.

Discussion for the JetBrains PhpStorm Package

Ground Rules:

  • This discussion is only about JetBrains PhpStorm and the JetBrains PhpStorm 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 JetBrains PhpStorm, 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