App
openfheorg / openfhe-development
This is the development repository for the OpenFHE library. The current version is 1.5.1 (released on April 10, 2026).
Claude Code, Cursor, Codex or VS Code. No key. You approve one sign-in in your browser.
Releases on GitHub (latest v1.6.1, Oct 9, 2026)
Repowise maps public repos from their source. Not affiliated with openfheorg. What is Repowise?
What is openfhe-development?
openfhe-development is the development repository for OpenFHE, an open-source library for fully homomorphic encryption, which allows computations over encrypted data without access to the secret key. The library implements several FHE schemes, including BFV and BGV for integer arithmetic and CKKS for real-number arithmetic. The codebase is written mainly in C++. Its code health is 6.7 out of 10 (Fair), ranked #172 of 4,000+ indexed repos. The last commit to openfhe-development was on Apr 9, 2026, and 34 people have contributed.
As of commit ed361af, indexed Jul 23, 2026. What it is comes from a model reading the README; the rest is measured from the source and git history, not from the maintainer.
For agentsopenfhe-development.md
Repo facts: type, license, health, rank, contributors
| Type | App |
|---|---|
| License | BSD-2-Clause |
| Code health | 6.7 / 10 (Fair) |
| Health rank | #172 of 4,000+ indexed repos |
| Last commit | Apr 9, 2026 |
| Contributors | 34 |
| Bus factor | 1 |
| Size | 569 files, 94,125 lines |
Explore openfhe-development
- DocumentationModule-by-module documentation, written from the source.
- ArchitectureDependency graph, layers and third-party dependencies.
- Code healthEvery file's score and the findings behind it.
- CommitsEach commit's effect on code health.
- OverviewEverything else the index found: contributors, decisions, what changed this week.
Ask about this code in your agent
This connects Repowise to openfhe-development's code. It does not install openfhe-development.
Useful if you want to change or fork openfhe-development: your agent can ask how it is put together and get answers that cite its files.
Ask about openfhe-development
Answers come from openfhe-development's README and source, with the files they cite. Two free answers a day without an account.
Want this for your own codebase? Map your repo free
About this page
Get a page like this for your own codebase
Repowise built this map of openfheorg/openfhe-development from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.
Free for 2 public repos, with a page like this one. No card. See how Repowise works
Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed. Star Repowise on GitHub
openfheorg/openfhe-development FAQ
What is openfhe-development?
openfhe-development is the development repository for the OpenFHE library, which supports computations over encrypted data without access to the secret key. It implements schemes such as BFV, BGV, CKKS and the FHEW/TFHE family. The repository is named openfheorg/openfhe-development.
How does openfhe-development work?
openfhe-development implements FHE schemes in C++ inside src, which holds 512 of its 569 files. Benchmarks in benchmark/src and documentation in docs sit alongside it. CMakeLists.txt defines how the library is built.
What language is openfhe-development written in?
openfhe-development is written mainly in C++, with 508 of its 569 files in cpp. Smaller parts are written in shell, C, makefile, Dockerfile and Python.
How is the openfhe-development code organized?
openfhe-development keeps its library code in src, benchmark programs in benchmark, and documentation in docs. Docker files are in docker, scripts are in scripts, and CI workflows are in .github/workflows.
When should I use openfhe-development?
openfhe-development is for computing over encrypted data without access to the secret key. It covers integer, real-number and Boolean circuit workloads under the schemes it implements.
What license does openfhe-development use?
openfhe-development is released under the BSD-2-Clause license. The license identifier is BSD-2-Clause.
Code health
On the leaderboards:#6 of 12 C++ repos
Key features of openfhe-development
- Brakerski/Fan-Vercauteren (BFV) and Brakerski-Gentry-Vaikuntanathan (BGV) schemes for integer arithmetic.
- Cheon-Kim-Kim-Song (CKKS) scheme for real-number arithmetic, including approximate bootstrapping.
- DM/FHEW, CGGI/TFHE and LMKCDEY schemes for evaluating Boolean circuits and arbitrary functions over larger plaintext spaces using lookup tables.
- Switching between CKKS and FHEW/TFHE to evaluate non-smooth functions such as comparison.
- Threshold FHE, interactive bootstrapping for Threshold CKKS, and Proxy Re-Encryption for BGV, BFV and CKKS.
How openfheorg/openfhe-development works
The library's code lives in src, which holds 512 of the repository's 569 files. The benchmark directory holds 26 files, including the benchmark/src programs Lattice.cpp, NbTheory.cpp, IntegerMath.cpp and VectorMath.cpp. CMakeLists.txt is the CMake build manifest that defines how the library is compiled. The docs directory holds 13 documentation files. .github/workflows/main.yml is a GitHub Actions workflow, one of several workflows in .github/workflows that run the repository's automated checks. The docker and scripts directories hold supporting files for container builds and scripts.
The codebase has 569 files and 7,234 symbols in 9 modules, led by C++, Shell and C. Code health is 6.7 out of 10, rated fair.
Maintain openfheorg/openfhe-development?
Claim this page, add a badge to the README, or re-index it.
Claim this page
Sign in with GitHub and we check that you are an admin or maintainer of openfheorg/openfhe-development. Then add a badge to the README that links readers here.
Add a badge to your README
Readers click through to this page and can ask openfhe-development's code a question. A badge also re-indexes the repo every week and marks you as the verified maintainer.
[](https://repowise.dev/repo/openfheorg/openfhe-development?src=badge_ask)Paste it at the top of README.md, under the title.
Added it already? Verify to get the mark now instead of tomorrow.
Need HTML or the larger health card? More formatsHide more formats
This badge as HTML
<a href="https://repowise.dev/repo/openfheorg/openfhe-development?src=badge_ask"><img src="https://api.repowise.dev/badge/wiki/openfheorg/openfhe-development.svg?label=ask" alt="repowise: Ask this codebase"></a>Code health card
The score, its change since the last index, and when it was measured. Follows the reader's light or dark theme.
<a href="https://repowise.dev/repo/openfheorg/openfhe-development?src=badge_card"><picture><source media="(prefers-color-scheme: light)" srcset="https://api.repowise.dev/badge/health/openfheorg/openfhe-development.svg?style=card&theme=light"><img src="https://api.repowise.dev/badge/health/openfheorg/openfhe-development.svg?style=card" alt="repowise code health" width="500" height="168"></picture></a>