Chocolatey
2.7.0 open-sourceFree plan: yes (checked 15 Oct) · Open source: yes
Starting price: not checked yet
The section your link pointed to isn't on Chocolatey's page any more, so we've brought you to the top.
Chocolatey is a package manager for Windows, similar to apt-get or yum, that automates software installation and management.
choco license
What you can do now
Summary
Chocolatey is an open-source package manager for Windows that automates the installation, upgrading, and management of third-party software packages via a command-line tool, and it is free to use. It is intended for system administrators who manage software inventory. The README positions it alongside package managers like apt-get or yum, and its usage requires the .NET Framework 4.8. The project shows continuous activity, having had 114 commits in the past year across 143 contributors.
Chocolatey is a package manager for Windows, similar to apt-get or yum, that automates software installation and management.
How Chocolatey helps
Which package provided a specific result during a search?
shows the source name in its output
What is the specific installation path for a package?
includes the software install path in the output of an information query
What source was used to install a package?
records and displays the source location used to install a package
Which version of a package is desired for an installation or upgrade?
allows pinning of a package version during installation or upgrade
What information is available about existing package templates?
can retrieve information about currently installed package templates
What is the current licensing status of a package?
provides a command to check the current licensing status
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for Chocolatey, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Chocolatey puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Commercials
pricing & packaging history · Chocolatey Software vendor page47 readings of Chocolatey Software's pricing page since Oct 2021, with 6 relaunches of its plan lineup and 1 change to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.
Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.
See plans → Already subscribed? Sign in →Plans by offering
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date. A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product. Readings that failed to show any plans are left out rather than read as a change.
Website history
chocolatey.org, every changeChocolatey Software's pricing and product pages and 12 more pages as they looked each month from October 2021 to November 2026: 28 renders, 0 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Brand changes
Each row is a name, owner or logo change we've confirmed. The dates are the last capture before it and the first one after. A new page design on its own isn't counted. Spot one that's wrong? Use “Not a rebrand” on its row.
We spotted these but haven't confirmed them yet, so they aren't counted above.
Releases
7 entries
No entries match these filters.
- March 20261
- December 20251
- July 20251
- May 20231
- October 20221
- March 20221
- January 20221
Project health
Issue, contributor and maintainer activity in chocolatey/choco, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.
- Contributors not measured distinct committers, last 12 months
- Maintainers not measured core set, last 12 months
- Bus factor not measured committers behind half the commits
- Community-filed 48% of issues opened, last 12 months
- Median time to close 11 days first maintainer reply 2 days
- Open backlog 489 of 2,759 issues ever filed
- Issues opened / month 2 · 4 communitymaintainers
- Open backlog 489
- Contributors / month not measured
- Commits / month not measured
- Stars not measured
- bugs 22%
- features 22%
- questions 6%
- other 50%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Articles
1 article · updated Nov 10, 2026Where Chocolatey turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.
Tutorials & guides 1
-
Install chocolatey in Windows 10/11
Learn the simple commands to install the Chocolatey package manager on Windows 11 using Terminal or PowerShell.
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.