Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

3,798

Downloads of v 0.8.6:

49

Last Update:

08 Jun 2024

Published Date:

08 Jun 2024

Reviewed Date:

10 Jun 2024

Reviewer:

gravatar

Package Maintainer(s):

Software Author(s):

  • Andy Boot

Tags:

gnu du unix cli foss

Dust

(Waiting for Maintainer to take corrective action)

  • 1
  • 2
  • 3

0.8.6 | Updated: 08 Jun 2024

Downloads:

3,798

Downloads of v 0.8.6:

49

Published:

08 Jun 2024

Reviewed:

10 Jun 2024

Reviewer:

gravatar

Maintainer(s):

Software Author(s):

  • Andy Boot

Tags:

gnu du unix cli foss

Dust 0.8.6

(Waiting for Maintainer to take corrective action)
  • 1
  • 2
  • 3

Some Checks Are Exempted or Have Failed

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Exemption:

Dependency requires reboot

Details

Scan Testing Resulted in Flagged as a Warning:

At least one file within this package has between 5 and 10 detections

Details
IMPORTANT

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

There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.

Starz0r (maintainer) on 23 Oct 2023 23:32:45 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 24 Oct 2023 00:09:31 +00:00:

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

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
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.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 24 Oct 2023 06:39:08 +00:00:

dust 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 6 and 10 VirusTotal detections associated with it.
This package version cannot be approved without an exemption from a Moderator.

Windos (reviewer) on 04 Dec 2023 06:46:17 +00:00:

Scanner Status Change - Virus Scanner has been set to rerun

chocolatey-ops (reviewer) on 04 Dec 2023 06:47:07 +00:00:

dust 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 6 and 10 VirusTotal detections associated with it.
This package version cannot be approved without an exemption from a Moderator.

flcdrg (reviewer) on 10 Dec 2023 23:19:17 +00:00:

As mentioned above, the number of VirusTotal detections is too high.

You will need to investigate whether there are real issues that need to be resolved in the software, or if these are false positives.

If the latter then please reply here as well as updating the package description with more info as to why the false positives may occur. You may also wish to follow up with the individual scanning engines that are flagging the software to see if you can get them to remove the false positive indications.

thanks,
David

Starz0r (maintainer) on 15 Dec 2023 16:39:31 +00:00:

These are false positives, having ran the software myself, I assume the pattern of scanning files got caught up by the anti-virus software.

Is there a way to follow up with the scanning engines that are erroneously marking this software as malicious? I'm not really sure of the process or how to do so, but I'd like to if possible.

flcdrg (reviewer) on 26 Dec 2023 21:33:47 +00:00:

Unfortunately I think it would require chasing up each one individually. I'm not sure if VirusTotal provides any easier way

David

Starz0r (maintainer) on 02 Jan 2024 07:44:38 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 02 Jan 2024 08:16:34 +00:00:

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

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
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.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 02 Jan 2024 08:28:31 +00:00:

dust 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 6 and 10 VirusTotal detections associated with it.
This package version cannot be approved without an exemption from a Moderator.

flcdrg (reviewer) on 26 Jan 2024 05:45:47 +00:00:

Retry scan.

If it still gets flagged, then:

  • A high VirusTotal detection score needs to be investigated, for example checking with the software author. Hopefully it is a false positive, but even open source software is not immune. eg. a 'supply chain' attack could compromise an otherwise innocent application. If the total remains in the range 5-10, then you will need to append a note to the description indicating why there are false positive results for this package.

thanks,
David
Scanner Status Change - Virus Scanner has been set to rerun

chocolatey-ops (reviewer) on 26 Jan 2024 05:52:03 +00:00:

dust 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 6 and 10 VirusTotal detections associated with it.
This package version cannot be approved without an exemption from a Moderator.

Starz0r (maintainer) on 05 Feb 2024 23:07:21 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 05 Feb 2024 23:46:25 +00:00:

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

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
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.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 05 Feb 2024 23:47:56 +00:00:

dust 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 6 and 10 VirusTotal detections associated with it.
This package version cannot be approved without an exemption from a Moderator.

TheCakeIsNaOH (reviewer) on 06 Feb 2024 05:22:31 +00:00:

Still looks like it has a high count of positives.

chocolatey-ops (reviewer) on 26 Feb 2024 05:26:11 +00:00:

We've found dust v0.8.6 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

  • Log in to the site and respond to the review comments.
  • Resubmit fixes for this version.
  • If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

Starz0r (maintainer) on 01 Mar 2024 22:22:14 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 01 Mar 2024 23:02:46 +00:00:

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

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
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.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 02 Mar 2024 00:35:34 +00:00:

dust 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 6 and 10 VirusTotal detections associated with it.
This package version cannot be approved without an exemption from a Moderator.

Windos (reviewer) on 03 Mar 2024 04:01:36 +00:00:

Please resolve these to allow this package to be approved:

  • A high VirusTotal detection score needs to be investigated, for example checking with the software author. Hopefully it is a false positive, but even open source software is not immune. eg. a 'supply chain' attack could compromise an otherwise innocent application. If the total remains in the range 6-10, then you will need to append a note to the description indicating why there are false positive results for this package.

Cheers,
Josh
Scanner Status Change - Virus Scanner has been set to rerun

chocolatey-ops (reviewer) on 03 Mar 2024 05:22:27 +00:00:

dust 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 6 and 10 VirusTotal detections associated with it.
This package version cannot be approved without an exemption from a Moderator.

Windos (reviewer) on 03 Mar 2024 08:31:58 +00:00:

Unfortunately, the AV detection count on this package is still between 6 and 10, please see my previous note about this.

chocolatey-ops (reviewer) on 23 Mar 2024 08:33:55 +00:00:

We've found dust v0.8.6 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

  • Log in to the site and respond to the review comments.
  • Resubmit fixes for this version.
  • If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

Starz0r (maintainer) on 25 Mar 2024 21:01:37 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 25 Mar 2024 21:42:20 +00:00:

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

  • Something went very wrong. There is no package to validate. Please repush package. If you receive this message again, contact the site admins.

Windos (reviewer) on 01 Apr 2024 02:01:10 +00:00:

Validation Status Change - Validation tests have been set to rerun.

chocolatey-ops (reviewer) on 01 Apr 2024 02:03:24 +00:00:

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

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
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.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 01 Apr 2024 02:05:58 +00:00:

dust 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 6 and 10 VirusTotal detections associated with it.
This package version cannot be approved without an exemption from a Moderator.

gep13 (reviewer) on 15 Apr 2024 19:26:09 +00:00:

There seems to be quite a high number of virus detections associated with a file contained within this package. Have there been any changes to the application that we should know about?

Starz0r (maintainer) on 22 Apr 2024 20:11:47 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 22 Apr 2024 20:46:35 +00:00:

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

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
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.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 22 Apr 2024 20:49:07 +00:00:

dust 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 6 and 10 VirusTotal detections associated with it.
This package version cannot be approved without an exemption from a Moderator.

Starz0r (maintainer) on 07 May 2024 19:58:51 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 07 May 2024 20:35:44 +00:00:

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

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
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.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 07 May 2024 21:01:50 +00:00:

dust 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 6 and 10 VirusTotal detections associated with it.
This package version cannot be approved without an exemption from a Moderator.

TheCakeIsNaOH (reviewer) on 17 May 2024 17:13:14 +00:00:

Hi, the count of Virustotal positives is high for this package version.

If there a known reason that this software may have a high rate of false positives, please link to the upstream documentation (for example it could be an issue or wiki) in the package description.
Then ask for an exemption and a moderator will review the documentation.
If there is not a known and documented reason, please contact the software authors to see if they have any reasons they can document.

Regards, TheCakeIsNaOH

Starz0r (maintainer) on 31 May 2024 14:55:36 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 31 May 2024 15:29:48 +00:00:

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

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
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.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 01 Jun 2024 18:47:49 +00:00:

dust 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 6 and 10 VirusTotal detections associated with it.
This package version cannot be approved without an exemption from a Moderator.

TheCakeIsNaOH (reviewer) on 02 Jun 2024 04:36:12 +00:00:

Hi,

I'm not seeing any changes to the virus status, or to the description.

Regards, TheCakeIsNaOH

Starz0r (maintainer) on 08 Jun 2024 20:50:12 +00:00:

User 'Starz0r' (maintainer) submitted package.

chocolatey-ops (reviewer) on 08 Jun 2024 21:35:48 +00:00:

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

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
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.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 08 Jun 2024 21:41:31 +00:00:

dust 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 6 and 10 VirusTotal detections associated with it.
This package version cannot be approved without an exemption from a Moderator.

TheCakeIsNaOH (reviewer) on 10 Jun 2024 23:23:21 +00:00:

Hi,

I'm not seeing any changes to the virus status, or to the description.

Regards, TheCakeIsNaOH

Description

Package Parameters

  • /GNU - Install GNU ABI executable instead of native MSVC ABI.

Build Status

du + rust = dust. Like du but more intuitive.

Demo

Example

Overview

Dust is meant to give you an instant overview of which directories are using disk space without requiring sort or head. Dust will print a maximum of one 'Did not have permissions message'.

Dust will list a slightly-less-than-the-terminal-height number of the biggest subdirectories or files and will smartly recurse down the tree to find the larger ones. There is no need for a '-d' flag or a '-h' flag. The largest subdirectories will be colored.

Usage

Usage: dust
Usage: dust <dir>
Usage: dust <dir>  <another_dir> <and_more>
Usage: dust -p <dir>  (full-path - does not shorten the path of the subdirectories)
Usage: dust -s <dir>  (apparent-size - shows the length of the file as opposed to the amount of disk space it uses)
Usage: dust -n 30  <dir>  (shows 30 directories instead of the default)
Usage: dust -d 3  <dir>  (shows 3 levels of subdirectories)
Usage: dust -r  <dir>  (reverse order of output, with root at the lowest)
Usage: dust -x  <dir>  (only show directories on the same filesystem)
Usage: dust -X ignore  <dir>  (ignore all files and directories with the name 'ignore')
Usage: dust -b <dir>  (do not show percentages or draw ASCII bars)

Note: Apparent-size is calculated slightly differently in dust to gdu. In dust each hard link is counted as using file_length space. In gdu only the first entry is counted.


legal\LICENSE.txt
                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.
legal\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

Package can be verified like this:

1. Go to https://github.com/bootandy/dust, enter to releases and download from there.

   i686:          https://github.com/bootandy/dust/releases/download/v0.8.6/dust-v0.8.6-i686-pc-windows-msvc.zip
   x86_64:        https://github.com/bootandy/dust/releases/download/v0.8.6/dust-v0.8.6-x86_64-pc-windows-msvc.zip
   i686-gnu:      https://github.com/bootandy/dust/releases/download/v0.8.6/dust-v0.8.6-i686-pc-windows-gnu.zip
   x86_64-gnu:    https://github.com/bootandy/dust/releases/download/v0.8.6/dust-v0.8.6-x86_64-pc-windows-gnu.zip

   to download the zip files. You may wish to rename one of the files.

2. You can use one of the following methods to obtain the SHA512 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'

   checksum:          65d9e89687b03151171cd2c7bcf3da98ec34545a3844c2732a1f365fa034f93c4a1bc46f45bac8f5382e22d34e815408a53bb3547d1fcecc4685bf3a6bd04a20
   checksum64:        2b09fcfbead2f4ebd9e5e7f41e5806499df1c278967093535289ad51eebd353352ee8c28fcfa5c6a9511457f1ac3f13dc4324b1ac99eef379ae4b1797f6a171c
   checksumgnu:       eb32da2bbb8e34ea77b1316bc8f04611665fbd598d6412ef58011e81380c7f789c3122446d7e0eca405318370541704b86cebf84dffb52fdc5709d925c3bb78a
   checksumgnu64:     bb6fe3b0acab5f0890d595ec849045bc8d28ebc2f4dddedf6be2760bae14b5563b33b376a76904cb0d2323ae945d5cc2f407c17bd622aa8ba1ef87622f62a3b3

File 'LICENSE.txt' obtained from:
   https://github.com/bootandy/dust/v0.8.6/LICENSE
tools\chocolateyinstall.ps1
$PackageName = 'dust';
$ToolsPath   = Split-Path -Parent $MyInvocation.MyCommand.Definition;
$PkgParams   = Get-PackageParameters;

$PrevInstallations = Get-ChildItem $ToolsPath;

if ($PkgParams.GNU) {
	$PackageArgs = @{
		PackageName    = $PackageName
		FileFullPath   = Get-Item $(Join-Path $ToolsPath 'dust-v0.8.6-i686-pc-windows-gnu.zip')
		FileFullPath64 = Get-Item $(Join-Path $ToolsPath 'dust-v0.8.6-x86_64-pc-windows-gnu.zip')
		Destination    = $ToolsPath
	};
} else {
	$PackageArgs = @{
		PackageName    = $PackageName
		FileFullPath   = Get-Item $(Join-Path $ToolsPath 'dust-v0.8.6-i686-pc-windows-msvc.zip')
		FileFullPath64 = Get-Item $(Join-Path $ToolsPath 'dust-v0.8.6-x86_64-pc-windows-msvc.zip')
		Destination    = $ToolsPath
	};
};

Get-ChocolateyUnzip @PackageArgs;

# cleanup
ForEach ($Installation in $PrevInstallations) {
	if (Test-Path -Path $Installation.FullName -PathType Container) {
		Remove-Item -Recurse -Force $Installation.FullName -EA 0;
	};
};
Remove-Item ($ToolsPath + '\*.' + 'zip');
tools\dust-v0.8.6-i686-pc-windows-gnu.zip
md5: AF7A9FAF702CD8061A4D593E44B7B75A | sha1: D8A4F8FAFB88EEC383FD3BC262FA313038DD6EB8 | sha256: 4D655425BE8D2EAD5E4CCA92CAF206ACE084A6619E253143FE346C6EEEEFFA8E | sha512: EB32DA2BBB8E34EA77B1316BC8F04611665FBD598D6412EF58011E81380C7F789C3122446D7E0ECA405318370541704B86CEBF84DFFB52FDC5709D925C3BB78A
tools\dust-v0.8.6-i686-pc-windows-msvc.zip
md5: A3237514E9BD60E9336C12B1E2949A01 | sha1: CD0DD5B5BF5DBBA41A4FCFE6CDD96F9F2ED075B4 | sha256: F77F02C1DC2125BC389EB7E8FB04EA3DC511770EDA4B20FAD55908D45087D8F5 | sha512: 65D9E89687B03151171CD2C7BCF3DA98EC34545A3844C2732A1F365FA034F93C4A1BC46F45BAC8F5382E22D34E815408A53BB3547D1FCECC4685BF3A6BD04A20
tools\dust-v0.8.6-x86_64-pc-windows-gnu.zip
md5: 017440DD95CEC74645ED244173C5324D | sha1: 6755DBEC668E6F71F2C3DD48DB693AA4E493B210 | sha256: C1C8469B0AC1BF61586B334E373507813C53F43F53B1232B06B5FFAFE6EEE5A1 | sha512: BB6FE3B0ACAB5F0890D595EC849045BC8D28EBC2F4DDDEDF6BE2760BAE14B5563B33B376A76904CB0D2323AE945D5CC2F407C17BD622AA8BA1EF87622F62A3B3
tools\dust-v0.8.6-x86_64-pc-windows-msvc.zip
md5: 38803B1C6BA9058E84DDF0CFD2A5B98F | sha1: D1069A94BD545BB94B1A3C5ECBF5AEF3F8FA034F | sha256: 8EAFE818BA2E2FE86EF02E9C67CCF7977D71F6614C3CA370429CD89B1BCE83FC | sha512: 2B09FCFBEAD2F4EBD9E5E7F41E5806499DF1C278967093535289AD51EEBD353352EE8C28FCFA5C6A9511457F1AC3F13DC4324B1AC99EEF379AE4B1797F6A171C

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
Dust 0.8.6 49 Saturday, June 8, 2024
Waiting for Maintainer
gravatar
Dust 0.8.4 112 Tuesday, March 7, 2023 Approved
Dust 0.8.3 355 Saturday, October 8, 2022 Approved
Dust 0.8.2 150 Tuesday, August 30, 2022 Approved
Dust 0.8.1 210 Wednesday, July 20, 2022 Approved
Dust 0.8.1-alpha2 61 Thursday, April 28, 2022 Approved
Dust 0.8.1-alpha1 51 Sunday, April 24, 2022 Approved
Dust 0.8.0 191 Thursday, April 21, 2022 Approved
Dust 0.7.5 284 Tuesday, September 28, 2021 Approved
Dust 0.7.1-alpha4 66 Thursday, September 23, 2021 Approved
Dust 0.7.1-alpha3 70 Thursday, September 23, 2021 Approved
Dust 0.6.2 193 Sunday, August 8, 2021 Approved
Dust 0.6.1 128 Tuesday, July 20, 2021 Approved
Dust 0.6.0 142 Thursday, June 24, 2021 Approved
Dust 0.5.4 211 Monday, January 18, 2021 Approved
Dust 0.5.3 139 Saturday, November 14, 2020 Approved
Dust 0.5.2 103 Saturday, November 14, 2020 Approved
Dust 0.5.1 109 Friday, November 6, 2020 Approved
Dust 0.5.0 96 Friday, November 6, 2020 Approved
Dust 0.4.41 88 Friday, November 6, 2020 Approved
Dust 0.4.5.0 110 Friday, October 2, 2020 Approved

Discussion for the Dust Package

Ground Rules:

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