vm-packages
open-sourceFree plan: not checked yet · Open source: yes (from the repository)
The section your link pointed to isn't on vm-packages's page any more, so we've brought you to the top.
What you can do now
Summary
vm-packages is an open-source set of PowerShell scripts that contain instructions for obtaining and configuring tools for use in FLARE VM and CommandoVM analysis environments. It is free to use and works by having analysis environments download and execute these scripts through the Chocolatey package manager. This set of packages is intended for security researchers, as its README mentions FLARE VM and the project focuses on malware analysis. Its documentation positions it alongside other environments that use Chocolatey for installation, and the project has seen 241 commits in the past year from 57 contributors.
How vm-packages helps
What tools need to be installed for FLARE VM or CommandoVM analysis environments?
The scripts contain instructions for obtaining and configuring tools via the Chocolatey package manager.
What is the source of the installation instructions for these analysis environments?
The packages are automatically built and pushed to a public package feed hosted on MyGet.
How is the installation process automated and tested for new packages?
Pull request automation tests packages to see if they build and install correctly.
What is the nature of the packages themselves?
The packages are PowerShell scripts containing only instructions for obtaining and configuring tools, and do not contain actual software distributions.
Where can the community contribute to suggest new tools or report bugs?
The packages are open-sourced, allowing the community to suggest new tools, improvements, and report bugs.
What is the dependency management system used for installation?
The installation of packages relies on Chocolatey.
Languages
Command line
| 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 vm-packages, 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 vm-packages 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…
Releases
Nothing shipped since we started watching. Releases and docs updates land here as they happen.
Project health
Issue, contributor and maintainer activity in mandiant/vm-packages, 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 52% of issues opened, last 12 months
- Median time to close 61 days first maintainer reply 6.2 days
- Open backlog 101 of 625 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 101
- Contributors / month not measured
- Commits / month not measured
- Stars not measured
- bugs 60%
- features 4%
- questions 4%
- other 32%
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
Libraries its release ships
What its latest release locks, checked against known advisories.We can only check tools that publish GitHub releases.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.