microsoft / SEAL
Microsoft SEAL is an easy-to-use and powerful homomorphic encryption library.
microsoft/SEAL holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (90/100) and lowest on Security (40/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.
Software health index
Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.
Score profile
Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.
The weighted overall 70 is calibrated to 83 on the published index scale (record calibration 2026-08-02).
Ownership
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
Development activity
How it's scored
| 36/36 | Push recency — last push 2 days ago |
| 10.4/36 | Commit cadence — 15/52 weeks with commits |
| 18/18 | Commit volume — 99 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 99 |
| human_commit_share | 1 |
| days_since_last_push | 2 |
| active_weeks_last_year | 15 |
Release discipline
How it's scored
| 27/27 | Ships releases — 55 releases published |
| 36/36 | Release recency — latest release 2 days ago |
| 27/27 | Release cadence — a release every ~8.5 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 55 |
| latest_release_tag | v4.7.1 |
| releases_from_tags | no |
| days_since_latest_release | 2 |
| mean_days_between_releases | 8.5 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 58.5/60 | Stars — 4,054 stars |
| 24.1/25 | Forks — 779 forks |
| 10.9/15 | Watchers — 93 watchers |
Inputs used
| forks | 779 |
| stars | 4,054 |
| watchers | 93 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (MIT) |
| 18/18 | CONTRIBUTING guide |
| 13.5/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | 0 |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | yes |
| readme_badge_services | — |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 5/22.5 | Commit distribution — top contributor authored 78% of commits |
| 13.5/13.5 | Contributor breadth — 46 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 46 |
| top_contributor_share | 0.777 |
How it's scored
| 34.6/42 | Issue resolution — 82% of issues closed |
| 18.9/30 | PR acceptance — 85/135 decided PRs merged |
| 13/13 | Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 85 |
| open_issues | 105 |
| closed_issues | 496 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 2 |
| prs_decided_30d | 2 |
| issue_closed_ratio | 0.825 |
| closed_unmerged_prs | 50 |
| first_time_authors_30d | 2 |
| first_time_prs_merged_30d | 2 |
| first_time_prs_decided_30d | 2 |
Ownership & stewardship
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 20/20 | Verified domain |
| 25/25 | Owner reach — 132,316 followers of microsoft |
| 25/25 | Track record — 8,392 public repos, account ~12 yr old |
Inputs used
| followers | 132,316 |
| owner_type | Organization |
| is_verified | yes |
| owner_login | microsoft |
| public_repos | 8,392 |
| account_age_days | 4,698 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 0/24 | CI workflows |
| 24/24 | Tests present |
| 16/16 | Linter config |
| 9.6/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — no data |
Inputs used
| has_ci | no |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | yes |
| has_precommit_config | yes |
Documentation
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://www.microsoft.com/en-us/research/group/cryptography-research/ |
| 10/10 | Repository description |
| 10/10 | Topics — 3 topics |
| 10/10 | Wiki |
Inputs used
| topics | encryption, cryptography, homomorphic-encryption |
| has_wiki | yes |
| homepage | https://www.microsoft.com/en-us/research/group/cryptography-research/ |
| docs_site | https://www.microsoft.com/en-us/research/group/cryptography-research/ |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
How it's scored
| 6.8/7.5 | Binary-Artifacts — binaries present in source code |
| 0/7.5 | Branch-Protection — no data |
| 0/2.5 | CI-Tests — no data |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
| 2.5/2.5 | Contributors — project has 4 contributing companies or organizations |
| 0/10 | Dangerous-Workflow — no data |
| 0/7.5 | Dependency-Update-Tool — no update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — no data |
| 0/5 | SAST — no SAST tool detected |
| 5/5 | Security-Policy — security policy file detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — no data |
| 0/7.5 | Vulnerabilities — 51 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 11 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 7 |
| scorecard_aggregate | 4 |
AI Readiness
How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.
Agent context & guidance
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 35.2/40 | Legible commit history — 66 of 100 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 0.66 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
Verify loop (build / test / typecheck)
How it's scored
| 18/18 | One-command bootstrap — tools/Makefile |
| 22/22 | Automated tests |
| 11/11 | Lint / format config |
| 11/11 | Static type checking — C++ (statically typed) |
| 0/10 | Reproducible environment |
| 10/10 | Demonstrated agent practice — 59 of the last 100 commits agent-authored or agent-credited |
| 0/8 | Automated maintenance — no automated dependency updates observed |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — no data |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | no |
| typed_language | yes |
| bootstrap_files | tools/Makefile |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | — |
| agent_commit_share | 0.59 |
| toolchain_manifests | android/app/build.gradle, android/build.gradle |
| dependency_bot_commit_share | 0 |
Code legibility for models
How it's scored
| 45/45 | Type-checkable code — C++ (statically typed) |
| 53/55 | Manageable file sizes — 10/271 source files over 60KB |
Inputs used
| primary_language | C++ |
| largest_source_bytes | 360,044 |
| source_files_sampled | 271 |
| oversized_source_files | 10 |
Machine-readable interfaces
How it's scored
| 0/40 | API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software |
| 0/20 | MCP server — not applicable to this kind of software |
| 40/40 | Runnable examples — examples |
Inputs used
| example_dirs | examples |
| has_mcp_signal | no |
| api_schema_files | — |
| interfaces_expected_of | — |
Key facts
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
More detail
Star and fork history 0 ★ / 779 ⇿
When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.
Each point covers 8 days.
OpenSSF Scorecard 4.0 / 10
Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).
| 9 | Binary-Artifacts | binaries present in source code |
| n/a | Branch-Protection | internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md |
| n/a | CI-Tests | no pull request found |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 0/30 approved changesets -- score normalized to 0 |
| 10 | Contributors | project has 4 contributing companies or organizations |
| n/a | Dangerous-Workflow | no workflows found |
| 0 | Dependency-Update-Tool | no update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| n/a | Packaging | packaging workflow not detected |
| n/a | Pinned-Dependencies | no dependencies found |
| 0 | SAST | no SAST tool detected |
| 10 | Security-Policy | security policy file detected |
| n/a | Signed-Releases | no releases found |
| n/a | Token-Permissions | No tokens found |
| 0 | Vulnerabilities | 51 existing vulnerabilities detected |
All dependencies 0
Full resolved dependency set from the GitHub dependency graph: 0 direct and 0 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|
Dependency advisories not assessed
Advisory matching could not run for this report: No resolved dependencies to assess
Raw JSON report machine-readable
Feedback
Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.
Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.
Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics.