|
| 1 | +# libmicrovmi |
| 2 | + |
| 3 | +<h3 align="center"> |
| 4 | + A cross-platform unified Virtual Machine Introspection API library |
| 5 | +</h3> |
| 6 | + |
| 7 | +<p align="center"> |
| 8 | + <a href="https://github.com/Wenzel/libmicrovmi/actions?query=workflow%3ACI"> |
| 9 | + <img src="https://github.com/Wenzel/libmicrovmi/workflows/CI/badge.svg" al="CI"/> |
| 10 | + </a> |
| 11 | + <a href="https://crates.io/crates/microvmi"> |
| 12 | + <img src="https://img.shields.io/crates/v/microvmi.svg" alt="crates.io"/> |
| 13 | + </a> |
| 14 | + <a href="https://docs.rs/microvmi"> |
| 15 | + <img src="https://docs.rs/microvmi/badge.svg" alt="docs.rs"> |
| 16 | + </a> |
| 17 | + <a href="https://gitter.im/libmicrovmi/community"> |
| 18 | + <img src="https://badges.gitter.im/libmicrovmi/community.svg" alt="gitter"> |
| 19 | + </a> |
| 20 | + <a href="https://gitpod.io/#https://github.com/Wenzel/libmicrovmi"> |
| 21 | + <img src="https://img.shields.io/badge/Gitpod-ready--to--code-blue?logo=gitpod" alt="gitpod"/> |
| 22 | + </a> |
| 23 | +</p> |
| 24 | +<p align="center"> |
| 25 | + <a href="https://libmicrovmi.github.io/"> |
| 26 | + <img src="https://img.shields.io/badge/Online-Documentation-green?style=for-the-badge&logo=gitbook" alt="online_docs"/> |
| 27 | + </a> |
| 28 | + |
| 29 | +</p> |
| 30 | + |
| 31 | +## Table of Contents |
| 32 | + |
| 33 | +- [Overview](#overview) |
| 34 | +- [Documentation](#documentation) |
| 35 | +- [Maintainers](#maintainers) |
| 36 | +- [License](#license) |
| 37 | + |
| 38 | +## Overview |
| 39 | + |
| 40 | +`libmicrovmi` aims to provide a cross-platform unified _Virtual Machine Introspection_ API. |
| 41 | + |
| 42 | +The term micro (μ) refers to the library's simplicity as well as the letter `U` |
| 43 | +standing for `Unified` interface. |
| 44 | + |
| 45 | +_Virtual Machine Introspection_ has been around since [2003](https://www.ndss-symposium.org/ndss2003/virtual-machine-introspection-based-architecture-intrusion-detection/), |
| 46 | +yet the ecosystem is still heavily fragmented and lacks standards as well as interoperability. |
| 47 | + |
| 48 | +See [Documentation: VMI Ecosystem Fragmentation](https://libmicrovmi.github.io/explanation/vmi_ecosystem.html) |
| 49 | + |
| 50 | +The main objective is to provide the simplest virtual machine introspection abstraction, offering a standard API to interact with |
| 51 | +any VMI provider. |
| 52 | + |
| 53 | + |
| 54 | + |
| 55 | +## Documentation |
| 56 | + |
| 57 | +Our documentation is available in `doc/` as an [`mdbook`](https://rust-lang.github.io/mdBook/) 📖 |
| 58 | + |
| 59 | +[](https://libmicrovmi.github.io/) |
| 60 | + |
| 61 | +To build the docs locally: |
| 62 | +~~~ |
| 63 | +$ cargo install mdbook |
| 64 | +$ mdbook build doc |
| 65 | +$ xdg-open doc/book/index.html |
| 66 | +~~~ |
| 67 | + |
| 68 | + |
| 69 | +## Maintainers |
| 70 | + |
| 71 | +- [@Wenzel](https://github.com/Wenzel) |
| 72 | +- [@rageagainsthepc](https://github.com/rageagainsthepc) |
| 73 | + |
| 74 | +## License |
| 75 | + |
| 76 | +[GNU General Public License v3.0](https://github.com/Wenzel/pyvmidbg/blob/master/LICENSE) |
0 commit comments