12 breaking releases

0.22.0 Sep 1, 2023
0.21.0 Jun 22, 2023
0.20.0 May 26, 2023
0.15.0 Feb 23, 2023
0.10.1 Oct 25, 2022

#138 in Web programming

Download history 34/week @ 2023-06-03 73/week @ 2023-06-10 112/week @ 2023-06-17 112/week @ 2023-06-24 74/week @ 2023-07-01 76/week @ 2023-07-08 206/week @ 2023-07-15 66/week @ 2023-07-22 74/week @ 2023-07-29 46/week @ 2023-08-05 72/week @ 2023-08-12 269/week @ 2023-08-19 145/week @ 2023-08-26 60/week @ 2023-09-02 39/week @ 2023-09-09 73/week @ 2023-09-16

349 downloads per month

MIT license


Project Freta


The Freta SDK enables access to Project Freta, a service used to inspect volatile memory images.

Included in this library is a utility, freta, which provides command line access to the Project Freta service.


  • Service Documentation contains information on how to use the Service and details to the information exposed by the Freta analysis.
  • CLI Reference contains information on how to use the Freta CLI to interact with the Freta service.
  • Module Documentation describes the APIs and data structures to programmatically interact with the Freta service.
  • Examples demonstrates how to build upon the SDK to automate Freta.


cargo install freta


The Freta client is written in Rust and requires Rust 1.64.0 (stable) or newer.

To build freta:

$ git clone https://github.com/microsoft/project-freta
$ cd project-freta
$ cargo build --release
$ ./target/release/freta --version

Using the Client

$ freta info
  "api_version": "0.7.2",
  "models_version": "0.9.0",
  "current_eula": "993C44214D3E5D0EEB92679E41FC0C4D69DA9C37EF97988FB724C7B2493695BB",
  "formats": [
$ freta images upload ~/projects/samples/centos-6-2.6.32-754.17.1.el6/OpenLogic\:CentOS\:6.10\:latest.lime
[2022-10-20T17:37:39Z INFO  freta] uploading as image id: 78f6bdc7-31ce-4877-a67e-f7137db248bd
206.99 MiB (25.26 MiB/s)
$ freta images list
      "last_updated": "2022-10-20T17:38:29.7311842Z",
      "owner_id": "72f988bf-86f1-41af-91ab-2d7cd011db47_09731d72-f8a6-463c-9efe-ca0bedfd82ae",
      "image_id": "78f6bdc7-31ce-4877-a67e-f7137db248bd",
      "state": "completed",
      "format": "lime",
      "tags": {},
      "shareable": false

Using Freta with automated tools

Instead of logging in as a user to the Freta service, automated tools can use the Azure service principals for authentication.

First, create a service principal:

$ az ad sp create-for-rbac -n YOUR_SERVICE_PRINCIPAL_NAME_HERE
  "appId": "00000000-0000-0000-0000-000000000000",

Then configure the freta client to use the newly created service principal, use the appId from the output of the previous command as the --client-id and the password as the --client-secret, and use the tenant as the --tenant-id:

$ freta config --client-id APP_ID_HERE --client-secret PASSWORD_HERE --tenant-id TENANT_HERE
[2023-01-04T19:43:34Z INFO  freta] config saved: Config { api url: "https://freta.microsoft.com/", client id: "00000000-0000-0000-0000-000000000000", tenant id: "REDACTED_TENANT_HERE", client secret: "[redacted]", scope: "api://a934fc14-92d7-4127-aecd-bddab35935da/.default" }

Before using the service, the service principal must agree to the Freta EULA. This can be done by running the following command:

$ freta eula accept

From here, the client can be used in an automated fashion.


This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repositories using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Reporting Security Issues

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.


~772K SLoC