Crates.io | osquery-rust |
lib.rs | osquery-rust |
version | 0.1.4 |
source | src |
created_at | 2022-03-02 02:20:52.44588 |
updated_at | 2024-05-09 19:34:59.417295 |
description | Rust bindings for Osquery |
homepage | https://github.com/polarlabs |
repository | https://github.com/polarlabs/osquery-rust |
max_upload_size | |
id | 541929 |
size | 117,881 |
This crate facilitates the development of Osquery extensions in Rust. Osquery communicates
with its extensions via an interface based on Apache Thrift. So, to put it simply,
osquery-rust
is a wrapper around that interface and turns it into a powerful API.
The crate is still in its early stages. However, it already works and got some traction in the beginning of 2024. Don't hesitate to create an issue on GitHub if it does not work as expected, you are missing something or have ideas on how to improve the API.
To get you inspired, have a look at the examples.
📝 An extension might provide multiple plugins. Not sure, how to do this
with osquery-rust
.
📝 Today, osquery-rust
is limited to table plugins. Osquery knows other plugins as well,
such as config and logger.
📝 Rethink API and align with Rust API Guidelines.
📝 Improve documentation and provide a tutorial.
✅ Publish a first example.
✅ Publish a working version of osquery-rust
on crates.io based PR merged into thrift 0.17.
✅ MVP, communicates with Osquery via socket and provides a table with data from /proc/meminfo.
✅ PR to Thrift to contribute the support for unix domain sockets to upstream. This was a preliminary to this project.
We do not follow Rust's naming convention for crates as usage of '-' and '_' in package and crate
names is not fully clear. So we follow the naming convention of Osquery. The Go bindings are
called osquery-go
. So, we named this crate osquery-rust
.
Thank you to all who build or contributed to these tools, as they enabled us to build this.