Downloads of v 3.36.0:


Last Update:

19 Jun 2021

Package Maintainer(s):

Software Author(s):

  • D. Richard Hipp
  • SQLite contributors


shell sqlite db database embedded hwaci

SQLite Shell

  • 1
  • 2
  • 3

3.36.0 | Updated: 19 Jun 2021



Downloads of v 3.36.0:


Software Author(s):

  • D. Richard Hipp
  • SQLite contributors

  • 1
  • 2
  • 3
SQLite Shell 3.36.0

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


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


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


To uninstall SQLite Shell, 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

  • 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 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. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade -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 -y --source="'STEP 3 URL'"

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

Exit $exitCode

- name: Ensure installed
    state: present
    version: 3.36.0
    source: STEP 3 URL

See docs at

chocolatey_package '' do
  action    :install
  version  '3.36.0'
  source   'STEP 3 URL'

See docs at

    Version: 3.36.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

   Name     = ''
   Ensure   = 'Present'
   Version  = '3.36.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { '':
  provider => 'chocolatey',
  ensure   => '3.36.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install version="3.36.0" source="STEP 3 URL"

See docs at

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 21 Jun 2021.


SQLite Shell is a command-line shell that allows the user to manually enter and execute SQL statements against an SQLite database.



  • This package is automatically updated using the Chocolatey Automatic Package Update Model (AU).
    If you find it is out of date by more than a day or two, please contact the maintainer(s) and let them know the package is no longer updating correctly.

SQLite Is Public Domain

 All of the code and documentation in SQLite has been dedicated to  the  public
 domain by the authors. All code authors, and representatives of the  companies
 they work for, have signed affidavits dedicating their  contributions  to  the
 public domain and originals  of  those  signed  affidavits  are  stored  in  a
 firesafe at the main  offices  of  Hwaci.  Anyone  is free  to  copy,  modify,
 publish, use, compile, sell, or distribute the original SQLite code, either in
 source code form or as a compiled  binary,  for  any  purpose,  commercial  or
 non-commercial, and by any means.

The previous paragraph applies to the deliverable  code  and  documentation  in
SQLite - those parts of the SQLite library that you actually  bundle  and  ship
with a larger application. Some scripts used as part of the build process  (for
example the "configure" scripts generated by autoconf) might fall  under  other
open-source licenses.  Nothing from these build scripts ever reaches the  final
deliverable SQLite library, however, and so the licenses associated with  those
scripts should not be a factor in assessing your rights to  copy  and  use  the
SQLite library.

All of the deliverable code in SQLite has been written from  scratch.  No  code
has been taken from other projects or from the open  internet.  Every  line  of
code can be traced back to its original author, and all of those  authors  have
public domain dedications on file.  So the SQLite code base  is  clean  and  is
uncontaminated with licensed code from other projects.

Open-Source, not Open-Contribution

SQLite is open-source, meaning that you can make as many copies of  it  as  you
want and do whatever you  want  with  those  copies,  without  limitation.  But
SQLite is not open-contribution.  In order to keep SQLite in the public  domain
and ensure that the code does  not  become  contaminated  with  proprietary  or
licensed content, the project does not accept patches from unknown persons.

All of the code in SQLite is original, having been written specifically for use
by SQLite.  No code has been copied from unknown sources on the internet.

Warranty of Title

SQLite is in the public domain and does not require a license.  Even  so,  some
organizations want legal proof of their  right  to  use  SQLite.  Circumstances
where this occurs include the following:

    * Your company desires indemnity against claims of copyright infringement.
    * You are using SQLite in a jurisdiction that does not recognize the public
    * You are using SQLite in a jurisdiction that does not recognize the right
      of an author to dedicate their work to the public domain.
    * You want to hold a tangible legal document as evidence that you have the
      legal right to use and distribute SQLite.
    * Your legal department tells you that you have to purchase a license.

If any of the above circumstances apply to you, Hwaci, the company that employs
all the developers of SQLite, will sell you a Warranty of Title for  SQLite.  A
Warranty of Title is a legal document that asserts that the claimed authors  of
SQLite are the true authors, and that the  authors  have  the  legal  right  to
dedicate the SQLite to the public domain, and that Hwaci will vigorously defend
against challenges to those claims.  All  proceeds  from  the  sale  of  SQLite
Warranties of Title are used to fund  continuing  improvement  and  support  of

Contributed Code

In order to keep SQLite completely  free  and  unencumbered  by  copyright, the
project does not accept patches. If you would like to make a suggested  change,
and include a patch as a proof-of-concept, that would be great.  However please
do not be offended if we rewrite your patch from scratch.

Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The application has been downloaded from the official distribution and can
be verified by:

1. Go to the binary distribution page
and download the archive using the link in
the Precompiled Binaries for Windows section.

Alternatively the archives can be downloaded directly from

2. Extract the file sqlite3.exe from the archive

3. The executable can be validated by comparing checksums
  - Use powershell function 'Get-Filehash' - Get-Filehash -algorithm sha256 sqlite3.exe
  - Use chocolatey utility 'checksum.exe' - checksum -t sha256 -f sqlite3.exe

  File:         sqlite3.exe
  ChecksumType: sha256
  Checksum:     A627642DE7BCDFCA7F8AFDC59346BF284D4059622C65ACB071C4420619447710
  Contents of file LICENSE.txt is obtained from
$ErrorActionPreference = 'Stop'

$toolsDir   = Split-Path -parent $MyInvocation.MyCommand.Definition
$executable = Get-ChildItem -Path $toolsDir 'sqlite?.exe' -Recurse

Install-BinFile -Name $executable.Name -Path $executable
$ErrorActionPreference = 'Stop'

$toolsDir   = Split-Path -parent $MyInvocation.MyCommand.Definition
$executable = Get-ChildItem -Path $toolsDir 'sqlite?.exe' -Recurse

Uninstall-BinFile -Name $executable.Name -Path $executable
md5: 9A554E5899B0B97FDA08F5D1D1595434 | sha1: 5D827A7CC97DF91713E4EF728BAE60E02EA17B4F | sha256: A627642DE7BCDFCA7F8AFDC59346BF284D4059622C65ACB071C4420619447710 | sha512: D43EE8E666697DEC6D96A5943D4A2C14B63BA3A245FE21F8AB92E5CB3CF08B50920419111D378652C625F53263E8C7794D79040799241F9E21AE15BF55B9DDD3

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.

Version Downloads Last Updated Status
SQLite Shell 3.35.5 882 Tuesday, April 20, 2021 Approved
SQLite Shell 3.35.4 441 Monday, April 12, 2021 Approved
SQLite Shell 3.35.3 20 Monday, April 12, 2021 Approved
SQLite Shell 3.35.2 28 Monday, April 12, 2021 Approved
SQLite Shell 3.35.1 13 Thursday, April 8, 2021 Approved
SQLite Shell 3.35.0 20 Wednesday, April 7, 2021 Approved
SQLite Shell 3.10.1 7240 Thursday, January 14, 2016 Approved
SQLite Shell 3.10.0 468 Wednesday, January 6, 2016 Approved
SQLite Shell 3.9.2 588 Monday, November 2, 2015 Approved

This package has no dependencies.

Discussion for the SQLite Shell Package

Ground Rules:

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