Downloads:

1,364

Downloads of v 0.1.7:

580

Last Update:

15 Nov 2019

Package Maintainer(s):

Software Author(s):

  • Teppei Fukuda

Tags:

trivy ci scan security docker image admin

Trivy

  • 1
  • 2
  • 3

0.1.7 | Updated: 15 Nov 2019

Downloads:

1,364

Downloads of v 0.1.7:

580

Maintainer(s):

Software Author(s):

  • Teppei Fukuda

  • 1
  • 2
  • 3
Trivy 0.1.7

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Failed

Details

Scan Testing Successful:

No detections found in any package files

Details

Deployment Method: Individual Install, Upgrade, & Uninstall

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

>

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

>

To uninstall Trivy, 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 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 trivy -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 trivy -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install trivy
  win_chocolatey:
    name: trivy
    version: '0.1.7'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'trivy' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.1.7'
end

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


cChocoPackageInstaller trivy
{
    Name     = "trivy"
    Version  = "0.1.7"
    Source   = "INTERNAL REPO URL"
}

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


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

This package was approved by moderator flcdrg on 30 Nov 2019.

Description

Trivy

Description

A Simple and Comprehensive Vulnerability Scanner for Containers, Suitable for CI - https://github.com/aquasecurity/trivy

Features

  • Install and uninstall via Chocolatey
  • Supports 32 and 64-bit version

Dependencies

Due to proper usage and DB update, package git is required.

Changelog

2019-11-14 Build 0.1.7

  • version 0.1.7

2019-08-25 Build 0.1.6

  • version 0.1.6

2019-08-22 Build 0.1.5

  • version 0.1.5

2019-07-08 Build 0.1.4

  • version 0.1.4

2019-06-27 Build 0.1.3

  • version 0.1.3

2019-06-07 Build 0.1.2

  • version 0.1.2

2019-05-27 Build 0.1.1

Usage

Package Parameters

  • /RefreshDB = (Yes/No) - If set to "Yes", after instalation Trivy will reset and update databases.

    If not set, then "No" is default answer

    Without git package instalation can take a while

Direct

choco install trivy -y

or with DB update during instalation

choco install trivy -y --params "/RefreshDB=Yes"

YAML (Foreman, puppetlabs/chocolatey module)

trivy:
  ensure: latest
  provider: chocolatey

or

trivy:
  ensure: latest

tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';

$packageName        = 'trivy'
$version            = '0.1.7'
$url64              = "https://github.com/aquasecurity/trivy/releases/download/v"+$version+"/trivy_"+$version+"_Windows-64bit.zip"
$url                = "https://github.com/aquasecurity/trivy/releases/download/v"+$version+"/trivy_"+$version+"_Windows-32bit.zip"
$checksum64         = "4000cda9964a4615aca1ecb29645049a2ba5dde44a61a76ad763ee5396e4ab32"
$checksum           = "3e1e3394208c6067e8e0d387373624507cb9c4f4eec74db1a67035f2aeb1c68c"
$bindir             = Join-Path $env:ChocolateyInstall "lib\trivy\tools\trivy.exe"

[regex]$refreshdbparams = “(?i)^(Yes|No)$”

$pp=Get-PackageParameters
if (!$pp['RefreshDB']) {$pp['RefreshDB']='No'}
else {
    if ($pp['RefreshDB'] -notmatch $refreshdbparams) {
      Write-Output "Wrong value $($pp.RefreshDB) for parameter RefreshDB"
      exit (1)
    }
}
$packageArgs = @{
  packageName     = $packageName
  fileType        = 'msi'
  url64bit        = $url64
  url             = $url
  UnzipLocation   = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"
  checksumType64  = 'sha256'
  checksumType    = 'sha256'
  checksum64      = $checksum64
  checksum        = $checksum
}

Install-ChocolateyZipPackage @packageArgs

# Write-Output $bindir
try {
    if ($($pp.RefreshDB) -eq "Yes") {
      Write-Output "Updating Trivy databases - it can take a while"
      & $bindir '--reset'
      & $bindir '--refresh' '--quiet'
    }
}
catch {
  # We don't care about updates, if they'll fail, do not fail package
  exit (0)
}

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
Trivy 0.1.6 148 Monday, August 26, 2019 Approved
Trivy 0.1.5 104 Thursday, August 22, 2019 Approved
Trivy 0.1.4 154 Monday, July 8, 2019 Approved
Trivy 0.1.3 129 Thursday, June 27, 2019 Approved
Trivy 0.1.2 138 Friday, June 7, 2019 Approved
Trivy 0.1.1 111 Thursday, June 6, 2019 Approved

    • git (≥ 2.17.0)
Discussion for the Trivy Package

Ground Rules:

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