Skip to main content
checksum package icon

checksum

checksum - Command line file checksum validator. checksum checks a file and returns a checksum for both md5 and sha1. To use checksum you would simply provide a file path and it will return the sum for the file. Example: checksum -f="relative\path" Example: checksum "relative\path" Example: checksum -f="c:\absolute\path" -t=sha1 You can also check against an existing signature. To validate against an existing signature (hash) you would simply provide the file and the expected signature. When checking a signature, if the signature is valid it exits with 0, otherwise it exits with a non-zero exit code. Example: checksum "c:\\path\to\somefile.exe" -c="thehash" Example: checksum -f="c:\\path\to\somefile.exe" -c="thehash" -t=sha1 SYNOPSIS checksum [-t=sha1|md5] [-c=signature] [-f=]filepath OPTIONS -?, --help, -h Prints out the options. -f, --file=VALUE REQUIRED: file - The is the name of the file. The file should exist -t, --type, --hashtype=VALUE Optional: hashtype - 'md5' or 'sha1' Defaults to 'md5'. -c, --check=VALUE Optional: check - the signature you want to check. Not case sensitive.

Total Downloads
8.4K
8,358
Published
Mar 2, 2014
Latest stable version

Install

.NET CLI
dotnet add package checksum --version 0.0.2
Package Manager Console
Install-Package checksum -Version 0.0.2
PackageReference
<PackageReference Include="checksum" Version="0.0.2" />

Frameworks

No framework metadata available.

Dependencies

No declared dependencies.

Adoption guide

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.

No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.