Ansible
PS DSC
Downloads:
27
Downloads of v 1.2.0:
27
Last Update:
29 Jul 2025
Published Date:
29 Jul 2025
Reviewed Date:
18 Jul 2025
Reviewer:
Package Maintainer(s):
Software Author(s):
- hjbdev
- Lotti
- ENG3PLabs
- oldreposcrapyard
- goodjun
- OliverWich
- EbouBaker
Tags:
pvm
(Maintainer updated, waiting for Reviewer)
- 1
- 2
- 3
1.2.0 | Updated: 29 Jul 2025
Downloads:
27
Downloads of v 1.2.0:
27
Published:
29 Jul 2025
Reviewed:
18 Jul 2025
Reviewer:
Maintainer(s):
Software Author(s):
- hjbdev
- Lotti
- ENG3PLabs
- oldreposcrapyard
- goodjun
- OliverWich
- EbouBaker
pvm 1.2.0
(Maintainer updated, waiting for Reviewer)
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by hjbdev, Lotti, ENG3PLabs, oldreposcrapyard, goodjun, OliverWich, EbouBaker. The inclusion of hjbdev, Lotti, ENG3PLabs, oldreposcrapyard, goodjun, OliverWich, EbouBaker trademark(s), if any, upon this webpage is solely to identify hjbdev, Lotti, ENG3PLabs, oldreposcrapyard, goodjun, OliverWich, EbouBaker goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.
- Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
- This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
- You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
- There are also no guarantees that it will be approved.
There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.
A PHP version manager to simply install different PHP versions and easily switch between them. Similar to nvm. Use pvm in the terminal after installation to get started. Repo: https://github.com/hjbdev/pvm
$ErrorActionPreference = 'Stop'
$packageName = "php-pvm"
$toolName = "pvm"
$userDataPath = [Environment]::GetFolderPath('UserProfile')
$targetPath = "$userDataPath\.$toolName"
if (Test-Path $targetPath) {
Remove-Item $targetPath -Force -Recurse
Write-Host "Removed the directory and all its contents from $targetPath"
}
Uninstall-ChocolateyPath $targetPath
Write-Host "Removed $targetPath from the system PATH"
$packageArgs = @{
packageName = $env:ChocolateyPackageName
softwareName = '$toolName*'
fileType = 'EXE'
silentArgs = "/qn /norestart"
validExitCodes= @(0, 3010, 1605, 1614, 1641)
}
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -eq 1) {
$key | % {
$packageArgs['file'] = "$($_.UninstallString)"
if ($packageArgs['fileType'] -eq 'MSI') {
$packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
$packageArgs['file'] = ''
} else {
}
Uninstall-ChocolateyPackage @packageArgs
}
} 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.
- pvm.exe (a764f8c2ee58) - ## / 71
- php-pvm.1.2.0.nupkg (161fb3166e0f) - ## / 67
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.
This package has no dependencies.
Ground Rules:
- This discussion is only about pvm and the pvm 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 pvm, 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.
tschogge (maintainer) on 06 Jun 2025 07:06:36 +00:00:
User 'tschogge' (maintainer) submitted package.
chocolatey-ops (reviewer) on 06 Jun 2025 07:39:33 +00:00:
php-pvm has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
tschogge (maintainer) on 06 Jun 2025 10:28:20 +00:00:
User 'tschogge' (maintainer) submitted package.
tschogge (maintainer) on 06 Jun 2025 10:56:32 +00:00:
User 'tschogge' (maintainer) submitted package.
chocolatey-ops (reviewer) on 06 Jun 2025 11:28:49 +00:00:
php-pvm has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
tschogge (maintainer) on 17 Jun 2025 21:46:49 +00:00:
User 'tschogge' (maintainer) submitted package.
chocolatey-ops (reviewer) on 17 Jun 2025 22:19:53 +00:00:
php-pvm has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 18 Jun 2025 01:18:05 +00:00:
php-pvm has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/2f7106a0d1d29cb66435222022fa92d8 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 18 Jun 2025 03:05:10 +00:00:
php-pvm has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has between 1 and 5 VirusTotal detections associated with it.
This is not enough detections to prevent the approval of this package version.
tschogge (maintainer) on 04 Jul 2025 19:20:35 +00:00:
When will the package be approved and listed in the community?
TheCakeIsNaOH (reviewer) on 05 Jul 2025 04:14:09 +00:00:
Hi,
Packages that are in a "ready for review" status and packages where the maintainer has updated/responded are put in a queue for human moderation. The moderators are primarily volunteers, so sometimes the packages for review can pile up somewhat.
You can go here https://ch0.co/moderation to see the current queue.
There are some items that should be addressed for this package:
ownersfield in the nuspec and the software author's name in theauthorsfield.VERIFICATION.txtwith explicit steps on how to verify the included binaries are the same as the binaries published by the project. Example: https://github.com/chocolatey-community/chocolatey-coreteampackages/blob/master/automatic/7zip.install/legal/VERIFICATION.txtLICENSE.txtor theVERIFICATION.txtto the location of the license for the softwareInstall-ChocolateyPathandUninstall-ChocolateyPathhelpers?Regards, TheCakeIsNaOH
tschogge (maintainer) on 15 Jul 2025 22:59:29 +00:00:
User 'tschogge' (maintainer) submitted package.
chocolatey-ops (reviewer) on 15 Jul 2025 23:30:57 +00:00:
php-pvm has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 15 Jul 2025 23:43:22 +00:00:
php-pvm has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/d3e7e34480d0152bcfb5c97023ce6e27 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 15 Jul 2025 23:58:26 +00:00:
php-pvm has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has between 1 and 5 VirusTotal detections associated with it.
This is not enough detections to prevent the approval of this package version.
flcdrg (reviewer) on 18 Jul 2025 03:25:15 +00:00:
Please resolve these to allow this package to be approved:
tools\LICENSE.txtandtools\VERIFICATION.txtincluded. If you're just downloading the file then you should not have those files.thanks,
David
tschogge (maintainer) on 29 Jul 2025 20:23:31 +00:00:
User 'tschogge' (maintainer) submitted package.
chocolatey-ops (reviewer) on 29 Jul 2025 20:56:56 +00:00:
php-pvm has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
chocolatey-ops (reviewer) on 29 Jul 2025 22:22:48 +00:00:
php-pvm has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/6c4e058b0d6db0c4d2fa92d64a36140e for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 29 Jul 2025 22:40:05 +00:00:
php-pvm has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has between 1 and 5 VirusTotal detections associated with it.
This is not enough detections to prevent the approval of this package version.