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...

Downloads:
390,196
Downloads of v 4.0.2:
58,328
Last Update:
13 Sep 2019
Package Maintainer(s):
Software Author(s):
- osquery
Tags:
InfoSec Tools
osquery
This is not the latest version of osquery available.
Downloads:
390,196
Downloads of v 4.0.2:
58,328
Software Author(s):
- osquery
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.
osquery 4.0.2
This is not the latest version of osquery available.
All Checks are Passing
2 Passing Test
To install osquery, run the following command from the command line or from PowerShell:
To upgrade osquery, run the following command from the command line or from PowerShell:
To uninstall osquery, 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 osquery --internalize --version=4.0.2 --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 osquery -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 osquery -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 osquery installed
win_chocolatey:
name: osquery
state: present
version: 4.0.2
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 'osquery' do
action :install
version '4.0.2'
source 'STEP 3 URL'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
Chocolatey::Ensure-Package
(
Name: osquery,
Version: 4.0.2,
Source: STEP 3 URL
);
Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.
cChocoPackageInstaller osquery
{
Name = 'osquery'
Ensure = 'Present'
Version = '4.0.2'
Source = 'STEP 3 URL'
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'osquery':
provider => 'chocolatey',
ensure => '4.0.2',
source => 'STEP 3 URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
salt '*' chocolatey.install osquery version="4.0.2" 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 as a trusted package on 05 Feb 2020.
osquery allows you to easily ask questions about your Linux, macOS, and
Windows infrastructure. Whether your goal is intrusion detection,
infrastructure reliability, or compliance, osquery gives you the ability
to empower and inform a broad set of organizations within your company.
### Package Parameters
* /InstallService
- This creates a new windows service that will auto-start the daemon.
These parameters can be passed to the installer with the user of -params
.
For example: -params '"/InstallService"'
.
md5: DFD67DBC9F708F603C869D7AE3A7BAA0 | sha1: 78273B4FC5FBD72CFFAA03D5E1A4502F565471D7 | sha256: D6275B80C7C5A91489F6764C1BCA65E4E73216F56D49D4BFCEB32E462D7A0ECC | sha512: 7805511CE07B1783D053C57FD4FCDD3E1811FEEE2F994BB127795155AE70E50455C2726BD7364E7A8F65D776FA80772DCA3A841BE16E6C353528B83AACC0AFF8
# Copyright (c) 2014-present, Facebook, Inc.
# All rights reserved.
#
# This source code is licensed in accordance with the terms specified in
# the LICENSE file found in the root directory of this source tree.
# This library file contains constant definitions and helper functions
#Requires -Version 3.0
. "$PSScriptRoot\\osquery_utils.ps1"
# Ensure the service is stopped and processes are not running if exists.
if ((Get-Service $serviceName -ErrorAction SilentlyContinue) -and `
(Get-Service $serviceName).Status -eq 'Running') {
Stop-Service $serviceName
# If we find zombie processes, ensure they're termintated
$proc = Get-Process | Where-Object { $_.ProcessName -eq 'osqueryd' }
if ($null -ne $proc) {
Stop-Process -Force $proc -ErrorAction SilentlyContinue
}
}
# Lastly, ensure that the Deny Write ACLs have been removed before modifying
if (Test-Path $daemonFolder) {
Set-DenyWriteAcl $daemonFolder 'Remove'
}
if (Test-Path $extensionsFolder) {
Set-DenyWriteAcl $extensionsFolder 'Remove'
}
# Copyright (c) 2014-present, Facebook, Inc.
# All rights reserved.
#
# This source code is licensed in accordance with the terms specified in
# the LICENSE file found in the root directory of this source tree.
# This library file contains constant definitions and helper functions
#Requires -Version 3.0
. "$PSScriptRoot\\osquery_utils.ps1"
$packageParameters = $env:chocolateyPackageParameters
$arguments = @{}
# Ensure the service is stopped and processes are not running if exists.
$svc = Get-WmiObject -ClassName Win32_Service -Filter "Name='osqueryd'"
if ($svc -and $svc.State -eq 'Running') {
Stop-Service $serviceName
# If we find zombie processes, ensure they're termintated
$proc = Get-Process | Where-Object { $_.ProcessName -eq 'osqueryd' }
if ($null -ne $proc) {
Stop-Process -Force $proc -ErrorAction SilentlyContinue
}
# If the service was installed using the legacy path in ProgramData, remove
# it and allow the service creation below to fix it up.
if ([regex]::escape($svc.PathName) -like [regex]::escape("${legacyInstall}*")) {
Get-CimInstance -ClassName Win32_Service -Filter "Name='osqueryd'" |
Invoke-CimMethod -MethodName Delete
}
}
# Lastly, ensure that the Deny Write ACLs have been removed before modifying
if (Test-Path $daemonFolder) {
Set-DenyWriteAcl $daemonFolder 'Remove'
}
if (Test-Path $extensionsFolder) {
Set-DenyWriteAcl $extensionsFolder 'Remove'
}
# Now parse the packageParameters using good old regular expression
if ($packageParameters) {
$match_pattern = "\/(?<option>([a-zA-Z]+)):(?<value>([`"'])?([a-zA-Z0-9- _\\:\.]+)([`"'])?)|\/(?<option>([a-zA-Z]+))"
$option_name = 'option'
$value_name = 'value'
if ($packageParameters -match $match_pattern ) {
$results = $packageParameters | Select-String $match_pattern -AllMatches
$results.matches | ForEach-Object {
$arguments.Add(
$_.Groups[$option_name].Value.Trim(),
$_.Groups[$value_name].Value.Trim())
}
} else {
Throw "Package Parameters were found but were invalid (REGEX Failure)"
}
if ($arguments.ContainsKey("InstallService")) {
$installService = $true
}
} else {
Write-Debug "No Package Parameters Passed in"
}
New-Item -Force -Type directory -Path $daemonFolder
New-Item -Force -Type directory -Path $logFolder
$packagePath = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)\\bin\\osquery.zip"
Get-ChocolateyUnzip -FileFullPath $packagePath -Destination $targetFolder
# In order to run osqueryd as a service, we need to have a folder that has a
# Deny Write ACL to everyone.
Move-Item -Force -Path $targetDaemonBin -Destination $destDaemonBin
Set-SafePermissions $daemonFolder
if ($installService) {
if (-not (Get-Service $serviceName -ErrorAction SilentlyContinue)) {
Write-Debug 'Installing osquery daemon service.'
# If the 'install' parameter is passed, we create a Windows service with
# the flag file in the default location in \Program Files\osquery\
# the flag file in the default location in Program Files
$cmd = '"{0}" --flagfile="C:\Program Files\osquery\osquery.flags"' -f $destDaemonBin
$svcArgs = @{
Name = $serviceName
BinaryPathName = $cmd
DisplayName = $serviceName
Description = $serviceDescription
StartupType = "Automatic"
}
New-Service @svcArgs
# If the osquery.flags file doesn't exist, we create a blank one.
if (-not (Test-Path "$targetFolder\osquery.flags")) {
Add-Content "$targetFolder\osquery.flags" $null
}
}
Start-Service $serviceName
}
# Add osquery binary path to machines path for ease of use.
Add-ToSystemPath $targetFolder
# Copyright (c) 2014-present, Facebook, Inc.
# All rights reserved.
#
# This source code is licensed in accordance with the terms specified in
# the LICENSE file found in the root directory of this source tree.
# This library file contains constant definitions and helper functions
#Requires -Version 3.0
. "$PSScriptRoot\\osquery_utils.ps1"
# Remove the osquery path from the System PATH variable. Note: Here
# we don't make use of our local vars, as Regex requires escaping the '\'
$oldPath = [System.Environment]::GetEnvironmentVariable('Path', 'Machine')
if ($oldPath -imatch [regex]::escape($targetFolder)) {
$newPath = $oldPath -replace [regex]::escape($targetFolder), $NULL
[System.Environment]::SetEnvironmentVariable('Path', $newPath, 'Machine')
}
if ((Get-Service $serviceName -ErrorAction SilentlyContinue)) {
Stop-Service $serviceName
# If we find zombie processes, ensure they're termintated
$proc = Get-Process | Where-Object { $_.ProcessName -eq 'osqueryd' }
if ($null -ne $proc) {
Stop-Process -Force $proc -ErrorAction SilentlyContinue
}
Set-Service $serviceName -startuptype 'manual'
Get-CimInstance -ClassName Win32_Service -Filter "Name='osqueryd'" | Invoke-CimMethod -methodName Delete
}
if (Test-Path $targetFolder) {
Remove-Item -Force -Recurse $targetFolder
} else {
Write-Debug 'osquery was not found on the system. Nothing to do.'
}
# License
By contributing to osquery you agree that your contributions will be licensed
under the terms of both the [LICENSE-Apache-2.0](LICENSE-Apache-2.0) and the
[LICENSE-GPL-2.0](LICENSE-GPL-2.0) files in the root of this source tree.
If you're using osquery you are free to choose one of the provided licenses.
`SPDX-License-Identifier: Apache-2.0 OR GPL-2.0-only`
# Copyright (c) 2014-present, Facebook, Inc.
# All rights reserved.
#
# This source code is licensed in accordance with the terms specified in
# the LICENSE file found in the root directory of this source tree.
# Force Powershell to use TLS 1.2
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls12
# The osquery installation happens in Program Files
$progFiles = [System.Environment]::GetEnvironmentVariable('ProgramFiles')
$targetFolder = Join-Path $progFiles 'osquery'
# Maintain the daemon and extension folders for "safe" permissions management
$daemonFolder = Join-Path $targetFolder 'osqueryd'
$extensionsFolder = Join-Path $targetFolder 'extensions'
$logFolder = Join-Path $targetFolder 'log'
# Maintain the binary paths for creating the system service and extraction
$targetDaemonBin = Join-Path $targetFolder "osqueryd.exe"
$destDaemonBin = Join-Path $daemonFolder "osqueryd.exe"
# Meta data for the system service installation
$serviceName = 'osqueryd'
$serviceDescription = 'osquery daemon service'
# Track the old installation paths for removal
$progData = [System.Environment]::GetEnvironmentVariable('ProgramData')
$legacyInstall = Join-Path $progData "osquery"
# Helper function to add an explicit Deny-Write ACE for the Everyone group
function Set-DenyWriteAcl {
[CmdletBinding(SupportsShouldProcess = $true, ConfirmImpact = "Medium")]
[OutputType('System.Boolean')]
param(
[string] $targetDir = '',
[string] $action = ''
)
if (($action -ine 'Add') -and ($action -ine 'Remove')) {
Write-Debug '[-] Invalid action in Set-DenyWriteAcl.'
return $false
}
if ($PSCmdlet.ShouldProcess($targetDir)) {
$acl = Get-Acl $targetDir
$inheritanceFlag = [System.Security.AccessControl.InheritanceFlags]::ContainerInherit -bor [System.Security.AccessControl.InheritanceFlags]::ObjectInherit
$propagationFlag = [System.Security.AccessControl.PropagationFlags]::None
$permType = [System.Security.AccessControl.AccessControlType]::Deny
$worldSIDObj = New-Object System.Security.Principal.SecurityIdentifier ('S-1-1-0')
$worldUser = $worldSIDObj.Translate([System.Security.Principal.NTAccount])
$permission = $worldUser.Value, "write", $inheritanceFlag, $propagationFlag, $permType
$accessRule = New-Object System.Security.AccessControl.FileSystemAccessRule $permission
# We only support adding or removing the ACL
if ($action -ieq 'add') {
$acl.SetAccessRule($accessRule)
} else {
$acl.RemoveAccessRule($accessRule)
}
Set-Acl $targetDir $acl
return $true
}
return $false
}
# A helper function to set "safe" permissions for osquery binaries
function Set-SafePermissions {
[CmdletBinding(SupportsShouldProcess = $true, ConfirmImpact = "Medium")]
[OutputType('System.Boolean')]
param(
[string] $target = ''
)
if ($PSCmdlet.ShouldProcess($target)) {
$acl = Get-Acl $target
# First, to ensure success, we remove the entirety of the ACL
$acl.SetAccessRuleProtection($true, $false)
foreach ($access in $acl.Access) {
$acl.RemoveAccessRule($access)
}
Set-Acl $target $acl
$acl = Get-Acl $target
$inheritanceFlag = [System.Security.AccessControl.InheritanceFlags]::ContainerInherit -bor [System.Security.AccessControl.InheritanceFlags]::ObjectInherit
$propagationFlag = [System.Security.AccessControl.PropagationFlags]::None
$permType = [System.Security.AccessControl.AccessControlType]::Allow
# "Safe" permissions in osquery entail the containing folder and binary both
# are owned by the Administrators group, as well as no account has Write
# permissions except for the Administrators group and SYSTEM account
$systemSid = New-Object System.Security.Principal.SecurityIdentifier('S-1-5-18')
$systemUser = $systemSid.Translate([System.Security.Principal.NTAccount])
$adminsSid = New-Object System.Security.Principal.SecurityIdentifier('S-1-5-32-544')
$adminsGroup = $adminsSid.Translate([System.Security.Principal.NTAccount])
$usersSid = New-Object System.Security.Principal.SecurityIdentifier('S-1-5-32-545')
$usersGroup = $usersSid.Translate([System.Security.Principal.NTAccount])
$permGroups = @($systemUser, $adminsGroup, $usersGroup)
foreach ($accnt in $permGroups) {
$grantedPerm = ''
if ($accnt -eq $usersGroup) {
$grantedPerm = 'ReadAndExecute'
} else {
$grantedPerm = 'FullControl'
}
$permission = $accnt.Value, $grantedPerm, $inheritanceFlag, $propagationFlag, $permType
$accessRule = New-Object System.Security.AccessControl.FileSystemAccessRule $permission
$acl.SetAccessRule($accessRule)
}
$acl.SetOwner($adminsGroup)
Set-Acl $target $acl
# Finally set the Administrators group as the owner for all items
$items = Get-ChildItem -Recurse -Path $target
foreach ($item in $items) {
$acl = Get-Acl -Path $item.FullName
$acl.SetOwner($adminsGroup)
Set-Acl $item.FullName $acl
}
return $true
}
return $false
}
# Helper function for running a .bat file from powershell
function Invoke-BatchFile {
param(
[string]$path,
[string]$parameters
)
$tempFile = [IO.Path]::GetTempFileName()
cmd.exe /c " `"$path`" $parameters && set > `"$tempFile`" "
Get-Content $tempFile | Foreach-Object {
if ($_ -match '^(.*?)=(.*)$') {
Set-Content "env:\$($matches[1])" $matches[2]
}
}
Remove-Item $tempFile
}
# Constructs a chocolatey .nuspec file in the current directory
function Write-NuSpec {
param(
[string] $packageName,
[string] $version,
[string] $authors,
[string] $owners,
[string] $projectSource,
[string] $packageSourceUrl,
[string] $copyright,
[string] $license
)
$nuspec = @"
<?xml version="1.0" encoding="utf-8"?>
<!-- Do not remove this test for UTF-8: if “Ω” doesn’t appear as greek uppercase omega letter enclosed in quotation marks, you should use an editor that supports UTF-8, not this one. -->
<package xmlns="http://schemas.microsoft.com/packaging/2015/06/nuspec.xsd">
<metadata>
<id>$packageName</id>
<title>$packageName</title>
<version>$version</version>
<authors>$authors</authors>
<owners>$owners</owners>
<summary>$packageName</summary>
<description>$packageName</description>
<projectUrl>$projectSource</projectUrl>
<packageSourceUrl>$packageSourceUrl</packageSourceUrl>
<tags>$packageName</tags>
<copyright>$copyright</copyright>
<licenseUrl>$license</licenseUrl>
<requireLicenseAcceptance>false</requireLicenseAcceptance>
</metadata>
<files>
<file src="local\**" target="local" />
</files>
</package>
"@
Out-File -Encoding "UTF8" -FilePath "$packageName.nuspec" -InputObject $nuspec
}
# Derive the location of the osquery build location
function Get-OsqueryBuildPath {
[OutputType('System.String')]
param()
$loc = Get-Location
$toks = $loc -Split '\\'
$ret = ''
0..$toks.length | ForEach-Object {
if (Test-Path "$($toks[0..$_] -Join '\')\tools\provision.ps1") {
$ret = "$($toks[0..$_] -Join '\')\build"
}
}
return $ret
}
# Helper function to add to the SYSTEM path
function Add-ToSystemPath {
param(
[string] $targetFolder = ''
)
$oldPath = [System.Environment]::GetEnvironmentVariable('Path', 'Machine')
if (-not ($oldPath -imatch [regex]::escape($targetFolder))) {
$newPath = $oldPath
if ($oldPath[-1] -eq ';') {
$newPath = $newPath + $targetFolder
} else {
$newPath = $newPath + ';' + $targetFolder
}
[System.Environment]::SetEnvironmentVariable('Path', $newPath, 'Machine')
}
}
# A helper function for starting and waiting on processes in powershell
function Start-OsqueryProcess {
param(
[string] $binaryPath = '',
[array] $binaryArgs = @(),
[bool] $redirectOutput = $true
)
$pinfo = New-Object System.Diagnostics.ProcessStartInfo
$pinfo.FileName = $binaryPath
$pinfo.RedirectStandardError = $redirectOutput
$pinfo.RedirectStandardOutput = $redirectOutput
$pinfo.UseShellExecute = $false
$pinfo.Arguments = $binaryArgs
$pinfo.WorkingDirectory = Get-Location
$p = New-Object System.Diagnostics.Process
$p.StartInfo = $pinfo
$p.Start()
$p.WaitForExit()
if ($redirectOutput) {
$stdout = $p.StandardOutput.ReadToEnd()
$stderr = $p.StandardError.ReadToEnd()
$exit = $p.ExitCode
[PSCustomObject] @{
stdout = $stdout
stderr = $stderr
exitcode = $exit
}
} else {
$exit = $p.ExitCode
[PSCustomObject] @{
exitcode = $exit
}
}
}
# A helper function to derive the latest VS install
function Get-VSInfo {
# Attempt to make use of vswhere to derive the build tools scripts
$vswhere = (Get-Command 'vswhere').Source
$vswhereArgs = @('-latest', '-legacy')
$vswhereOut = (Start-OsqueryProcess $vswhere $vswhereArgs).stdout
$vsinfo = New-Object -TypeName psobject
$vsinfo | Add-Member -MemberType NoteProperty -Name version -Value ''
$vsinfo | Add-Member -MemberType NoteProperty -Name location -Value ''
foreach ($l in $vswhereOut.split([environment]::NewLine)) {
$toks = $l.split(":")
if ($toks.Length -lt 2) {
continue
}
if ($toks[0].trim() -like 'installationVersion') {
$vsinfo.version = $toks[1].Split(".")[0]
}
if ($toks[0].trim() -like 'installationPath') {
$vsinfo.location = [System.String]::Join(":", $toks[1..$toks.Length])
}
}
$vsinfo.location = $vsinfo.location.trim()
$vsinfo.version = $vsinfo.version.trim()
return $vsinfo
}
# A helper function to derive the latest VS install and call vcvarsall.bat
function Invoke-VcVarsAll {
$vsinfo = Get-VSInfo
$vsLoc = $vsinfo.location
$vsVersion = $vsinfo.version
if ($vsLoc -ne '') {
$vcvarsall = Join-Path $vsLoc 'VC'
if ($vsVersion -eq '15') {
$vcvarsall = Join-Path $vcvarsall '\Auxiliary\Build\vcvarsall.bat'
} else {
$vcvarsall = Join-Path $vcvarsall 'vcvarsall.bat'
}
# Lastly invoke the environment provisioning script
$null = Invoke-BatchFile "$vcvarsall" "amd64"
return $true
}
# As a last ditch effort, attempt to find the env variables set by VS2015
# in order to derive the location of vcvarsall
$vsComnTools = [environment]::GetEnvironmentVariable("VS140COMNTOOLS")
if ($vsComnTools -eq '') {
return $false
}
$vcvarsall = Resolve-Path $(Join-Path "$vsComnTools" "..\..\VC")
$vcvarsall = Join-Path $vcvarsall 'vcvarsall.bat'
$null = Invoke-BatchFile "$vcvarsall" "amd64"
return $true
}
To verify the osquery binaries are valid and not corrupted, one can run one of the following:
C:\Users\> Get-FileHash -Algorithm SHA256 C:\Program Files\osquery\osqueryd\osqueryd.exe
C:\Users\> Get-FileHash -Algorithm SHA1 C:\Program Files\osquery\osqueryd\osqueryd.exe
C:\Users\> Get-FileHash -Algorithm MD5 C:\Program Files\osquery\osqueryd\osqueryd.exe
And verify that the digests match one of the below values:
SHA256: 1ED387063092FC982076F821F0A3583517EBFF83C3E377DFF3A89E758D7DCC60
SHA1: F6B7435D6763EF93B7A750EB167A48833B1F1A7D
MD5: A36718DBD5D4218CB0ED38C1813BB15A
Log in or click on link to see number of positives.
- osquery.4.0.2.nupkg (990bfeace573) - ## / 57
- osquery.zip (d6275b80c7c5) - ## / 61
- osqueryd.exe (1ed387063092) - ## / 70
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 |
---|---|---|---|
osquery 4.5.1 | 12840 | Monday, November 9, 2020 | Approved |
osquery 4.5.0 | 10081 | Thursday, October 1, 2020 | Approved |
osquery 4.4.0 | 12890 | Friday, July 31, 2020 | Approved |
osquery 4.3.0 | 20834 | Saturday, May 9, 2020 | Approved |
osquery 4.2.0 | 28928 | Tuesday, February 25, 2020 | Approved |
osquery 4.0.2 | 58328 | Friday, September 13, 2019 | Approved |
osquery 4.0.1 | 492 | Wednesday, September 11, 2019 | Approved |
osquery 3.4.0 | 9514 | Thursday, May 23, 2019 | Approved |
osquery 3.3.2 | 31574 | Monday, January 28, 2019 | Approved |
osquery 3.3.1 | 43551 | Tuesday, October 2, 2018 | Approved |
osquery 3.3.0 | 3170 | Monday, August 20, 2018 | Approved |
osquery 3.2.9 | 74676 | Monday, July 2, 2018 | Approved |
osquery 3.2.6 | 52723 | Monday, July 2, 2018 | Approved |
osquery 3.2.4 | 3011 | Friday, May 4, 2018 | Approved |
osquery 2.11.2 | 5626 | Monday, February 5, 2018 | Approved |
osquery 2.11.0 | 1955 | Friday, January 12, 2018 | Approved |
osquery 2.10.4 | 1763 | Sunday, December 3, 2017 | Approved |
osquery 2.10.2 | 956 | Thursday, November 16, 2017 | Approved |
osquery 2.9.0 | 2393 | Friday, October 20, 2017 | Approved |
osquery 2.8.0 | 1243 | Wednesday, September 27, 2017 | Approved |
osquery 2.7.0 | 1372 | Wednesday, August 23, 2017 | Approved |
osquery 2.6.1 | 816 | Sunday, August 6, 2017 | Approved |
osquery 2.6.0 | 531 | Friday, July 28, 2017 | Approved |
osquery 2.5.0 | 4548 | Tuesday, June 20, 2017 | Approved |
osquery 2.4.2 | 1343 | Tuesday, May 9, 2017 | Approved |
osquery 2.4.0 | 744 | Saturday, April 15, 2017 | Approved |
osquery 2.3.2 | 1440 | Thursday, February 16, 2017 | Approved |
osquery 2.2.1 | 733 | Thursday, December 22, 2016 | Approved |
osquery 2.2.1-gd6630be | 350 | Tuesday, December 27, 2016 | Exempted |
osquery 2.2.0 | 394 | Tuesday, December 13, 2016 | Approved |
osquery 2.1.1 | 584 | Thursday, November 3, 2016 | Approved |
osquery 2.0.0 | 632 | Tuesday, October 11, 2016 | Approved |
Copyright (c) 2014-present, Facebook, Inc. All rights reserved.
This package has no dependencies.
Ground Rules:
- This discussion is only about osquery and the osquery 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 osquery, 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.