AVML
v0.21.0 open-sourceThe section your link pointed to isn't on AVML's page any more, so we've brought you to the top.
AVML - Acquire Volatile Memory for Linux
avml stream blob ${SAS_URL}
nc -l 9000 > snapshot.lime
# then on the target:
avml stream tcp collector.example.com:9000
avml --max-disk-available-pct 50 /tmp/memdump
avml-convert --version
Summary
AVML is an open-source command-line tool for acquiring volatile memory from Linux hosts, written in Rust and distributed as a static binary so it can run on a target without knowing its distribution or kernel in advance, and without on-target compilation. It reads memory from /dev/crash, /proc/kcore, or /dev/mem, and can save locally, upload to Azure Blob Storage or HTTP, or stream a live snapshot directly to Azure Blob or a raw TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it. listener with no local file written, which matters for read-only roots or chain-of-custody requirements. This fits DFIRDFIRDigital forensics and incident response, investigating what happened during a security incident and containing it. The work includes preserving evidence, reconstructing activity and restoring systems. practitioners and incident responders doing memory forensics on Linux systems. First committed in 2019, it has 13 contributors and stayed active with 103 commits and 12 releases in the past year, the latest 44 days ago.
AVML - Acquire Volatile Memory for Linux
How AVML helps
What did this machine's RAM actually contain at the moment I hit it?
reads physical memory directly from /dev/crash, /proc/kcore, or /dev/mem and writes it out in LiME format for downstream analysis with standard memory forensics tools
How do I get a memory image off this host without leaving a forensic footprint on its disk?
streams the snapshot directly to Azure Blob or a raw TCP listener as it reads, so no local file is ever written, which holds even on a read-only root
Which memory interface will actually work on this box without knowing its distribution or kernel ahead of time?
iterates over the available sources in turn and uses the first one that functions, so the same static binary works across the distribution and kernel versions it has been run against
Is this host's kernel configuration going to block acquisition entirely?
fails to acquire memory when the kernel lockdown feature is enabled, since that feature blocks the raw memory access all of the sources depend on
How do I get an image off a host with no free disk space to hold one?
uploads to Azure Blob Storage or over HTTP after capture, or streams straight to a destination as it reads so nothing has to land on the target's disk at all
Do I need to move this capture into a different format before my tooling can read it?
converts between the AVML, LiME, and raw formats after the fact, so an image captured in one form can be reshaped for whatever the analysis pipeline expects
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 AVML, 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 AVML 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 · Microsoft vendor page16 readings of Microsoft's pricing page since Mar 2022, with 3 relaunches of its plan lineup — 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
microsoft.com, every changeMicrosoft's home page and 40 more pages as they looked each month from October 2021 to October 2026: 1520 renders, 335 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
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Coverage
Missing something? Tell us
What AVML connects to, runs on and detects, read from its release notes and docs. So far: 1 updated supported platform.
1 change, tracked since Oct 9, 2026.
-
Oct 92026
updated Azure VM test matrix refresh
Refresh Azure VM image matrix and harden Azure testing by @demoray in https://github.com/microsoft/avml/pull/880
Other 1
Nothing first seen in this window. That doesn't mean AVML shipped nothing, only that we found no record of it.
How we count
Read from 1 of 9 release notes and docs updates we hold for AVML. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through AVML's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
9 entries
No entries match these filters.
- October 20261
- July 20261
- June 20261
- May 20261
- March 20251
- January 20231
- June 20221
- February 20221
- January 20221
Project health
Issue, contributor and maintainer activity in microsoft/avml, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 4 +2 vs prior 12 months
- Maintainers 1 +2 joined · −2 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 2.3 days first maintainer reply 35 hours
- Open backlog 4 of 29 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 4
- Contributors / month 0
- Commits / month 0
- Stars 1,120
- other 100%
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.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.
Choose a badge style and copy the code →