Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...
- Passing
- Failing
- Pending
- Unknown / Exempted

Downloads:
25,864
Downloads of v 2.3.0:
7,455
Last Update:
02 Nov 2019
Package Maintainer(s):
Software Author(s):
- Haxe Foundation
Tags:
neko haxe vm admin
Neko
Downloads:
25,864
Downloads of v 2.3.0:
7,455
Maintainer(s):
Software Author(s):
- Haxe Foundation
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
All Checks are Passing
2 Passing Test
To install Neko, run the following command from the command line or from PowerShell:
To upgrade Neko, run the following command from the command line or from PowerShell:
To uninstall Neko, run the following command from the command line or from PowerShell:
NOTE: This applies to both open source and commercial editions of Chocolatey.
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://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
choco download neko --internalize --source=https://chocolatey.org/api/v2
(additional options) - Run
choco push --source="'http://internal/odata/repo'"
for package and dependencies - Automate package internalization
- Run
3. Enter your internal repository url
(this should look similar to https://chocolatey.org/api/v2)
4. Choose your deployment method:
choco upgrade neko -y --source="'STEP 3 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 neko -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Ensure neko installed
win_chocolatey:
name: neko
state: present
version: 2.3.0
source: STEP 3 URL
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
Coming early 2020! Central Managment Reporting available now! More information...
chocolatey_package 'neko' do
action :install
version '2.3.0'
source 'STEP 3 URL'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
Chocolatey::Ensure-Package
(
Name: neko,
Version: 2.3.0,
Source: STEP 3 URL
);
Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.
cChocoPackageInstaller neko
{
Name = 'neko'
Ensure = 'Present'
Version = '2.3.0'
Source = 'STEP 3 URL'
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'neko':
provider => 'chocolatey',
ensure => '2.3.0',
source => 'STEP 3 URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
salt '*' chocolatey.install neko version="2.3.0" source="STEP 3 URL"
See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.
5. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved by moderator mwallner on 05 Nov 2019.
Neko is a lightweight and yet well optimized virtual machine. The VM can be easily embedded into any application and your libraries can be accessed using the C foreign function interface.
$packDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
Install-ChocolateyZipPackage `
-PackageName 'neko' `
-UnzipLocation "$packDir" `
-Url "$packDir\neko-*-win.zip" `
-Checksum 'fe5a11350d2dd74338f971d62115f2bd21ec6912f193db04c5d28eb987a50485' `
-ChecksumType 'sha256' `
-Url64bit "$packDir\neko-*-win64.zip" `
-Checksum64 'd09fdf362cd2e3274f6c8528be7211663260c3a5323ce893b7637c2818995f0b' `
-ChecksumType64 'sha256'
$nekoDir = "$(Get-Item "$packDir/neko-*-win*" -Exclude "*.zip")"
# Install the dll files to C:\ProgramData\chocolatey\bin
# It is because they are loaded by other neko binaries, e.g. haxelib.exe
$chocoBin = Join-Path $env:ChocolateyInstall 'bin'
$dllFiles = @('gcmt-dll.dll', 'neko.dll')
foreach ($file in $dllFiles) {
Copy-Item "$nekoDir/$file" "$chocoBin"
}
# Set NEKOPATH such that the ndll files can be loaded.
Install-ChocolateyEnvironmentVariable -VariableName NEKOPATH -VariableValue $nekoDir
# Remove the dll files from C:\ProgramData\chocolatey\bin
$chocoBin = Join-Path $env:ChocolateyInstall 'bin'
$dllFiles = @('gcmt-dll.dll', 'neko.dll')
foreach ($file in $dllFiles) {
$dllFile = Join-Path $chocoBin $file
Remove-Item "$dllFile"
}
Uninstall-ChocolateyEnvironmentVariable -VariableName NEKOPATH
md5: 56B98C966128800497BA8E0D94688C70 | sha1: DFAFC8CA5B39EC1CAF4843CE066B5FC9F080DA4B | sha256: FE5A11350D2DD74338F971D62115F2BD21EC6912F193DB04C5D28EB987A50485 | sha512: 40E831BE3B272BCEBC8B48AA50B84271B84B2F10CC69A71CC085DDB7C5C4F35D254E3ED6E1BFE74B40BF143F764CA426FD1AFE9909AEEA92D470A8125F7B4DD0
md5: A26A3581AD1796EDD35C9F2A0AB01D9E | sha1: 5EC8505B12A696C01A330E60757CED72EBAD8610 | sha256: D09FDF362CD2E3274F6C8528BE7211663260C3A5323CE893B7637C2818995F0B | sha512: 597BE30B0D7DBE162206585BA3FDB52D0E10159F3AD7589CE8D7785D986DC8D0964FF5612F8E9D1586F7C5EE7ABD6ABB8602797F4F7B332B6D6EEB10718FD441
Packager (Andy Li) is a member of the Haxe Foundation.
The files included in this package are the "Windows Binaries" available at https://github.com/HaxeFoundation/neko/releases.
Log in or click on link to see number of positives.
- msvcp140.dll (9c1dc36d3193) - ## / 69
- vcruntime140.dll (6823b98c3e92) - ## / 71
- msvcp140.dll (517cd3aac217) - ## / 70
- vcruntime140.dll (d89c7b863fc1) - ## / 72
- neko-2.3.0-win.zip (fe5a11350d2d) - ## / 61
- neko-2.3.0-win64.zip (d09fdf362cd2) - ## / 61
- neko.2.3.0.nupkg (a9576c35c9c2) - ## / 61
- gcmt-dll.dll (009989ddbf33) - ## / 66
- neko.dll (00037f818e37) - ## / 67
- neko.exe (49fa0346526f) - ## / 68
- nekoc.exe (b2db9c61353f) - ## / 65
- nekoml.exe (33155ea21e33) - ## / 72
- nekotools.exe (271f0159be24) - ## / 72
- gcmt-dll.dll (53789b334ed6) - ## / 68
- neko.dll (c8e1557ed895) - ## / 69
- neko.exe (8ca4143387b4) - ## / 69
- nekoc.exe (ebf31d15b2c1) - ## / 71
- nekoml.exe (91d4411e61ac) - ## / 67
- nekotools.exe (db641a2b6bd9) - ## / 69
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.
Version | Downloads | Last Updated | Status |
---|---|---|---|
Neko 2.3.0 | 7455 | Saturday, November 2, 2019 | Approved |
Neko 2.2.0 | 8184 | Thursday, December 28, 2017 | Approved |
Neko 2.1.0 | 7231 | Sunday, May 8, 2016 | Approved |
Neko 2.0.0 | 2994 | Monday, March 16, 2015 | Approved |
-
- vcredist2015 (≥ 14.0.24215.20170201)
Ground Rules:
- This discussion is only about Neko and the Neko 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 Neko, 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.