Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 03:14 UTC

bcgit / bc-csharp

BouncyCastle.NET Cryptography Library (Mirror)

C#MIT★ 1,930 stars⑂ 609 forkssince Jun 2013View on GitHub ↗

bcgit/bc-csharp holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Community & Adoption (87/100) and lowest on Sustainability & Governance (55/100). It was last updated 23 days ago. A single contributor accounts for most of its recent work.

77
overall / 100
Good

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.

77
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

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 66 is calibrated to 77 on the published index scale (record calibration 2026-08-02).

Ownership

312 followers9 public repossince May 2013

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetBouncyCastle.Cryptography2.7.0-1481 days agobouncycastlecryptographydtlsencryptionopen-sourceopenpgppost-quantumsecuritytls

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

66Good · 21% of overall
How it's scored
28.8/36Push recency — last push 23 days ago
32.5/36Commit cadence — 47/52 weeks with commits
18/18Commit volume — 747 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 27 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year747
human_commit_share1
days_since_last_push23
active_weeks_last_year47
How it's scored
16.2/27Ships releases — 2 version tags (no GitHub releases)
0/36Release recency — latest release 4,260 days ago
12.6/27Release cadence — a release every ~357.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count2
latest_release_tag1.8.0-beta4-update1
releases_from_tagsyes
days_since_latest_release4,260
mean_days_between_releases357.9
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

87Excellent · 17% of overall
How it's scored
53.3/60Stars — 1,930 stars
23.2/25Forks — 609 forks
11.1/15Watchers — 101 watchers
Inputs used
forks609
stars1,930
watchers101
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
80/80Total downloads — 457,791,598 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesBouncyCastle.Cryptography
dependents—
ecosystemsnuget
total_downloads457,791,598
monthly_downloads—
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

55Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.7/22.5Commit distribution — top contributor authored 88% of commits
13.5/13.5Contributor breadth — 43 contributors
10/10OpenSSF Scorecard: Contributors — project has 20 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled43
top_contributor_share0.882
How it's scored
31.1/42Issue resolution — 74% of issues closed
0.5/30PR acceptance — 3/178 decided PRs merged
0/13Newcomer PR acceptance — 0/5 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs3
open_issues113
closed_issues323
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d5
issue_closed_ratio0.741
closed_unmerged_prs175
first_time_authors_30d2
first_time_prs_merged_30d0
first_time_prs_decided_30d5
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
17.9/25Owner reach — 312 followers of bcgit
19.3/25Track record — 9 public repos, account ~13 yr old
Inputs used
followers312
owner_typeOrganization
is_verifiedno
owner_loginbcgit
public_repos9
account_age_days4,890

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on nuget
35/35Publish recency — latest publish 81 days ago
20/20Version history — 14 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesBouncyCastle.Cryptography
ecosystemsnuget
any_deprecatedno
min_days_since_publish81

Engineering Quality

Are baseline engineering and documentation practices in place?

63Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://www.bouncycastle.org/csharp
10/10Repository description
10/10Topics — 9 topics
10/10Wiki
Inputs used
topicsbouncycastle, cryptography, dtls, encryption, open-source, openpgp, post-quantum, security, tls
has_wikiyes
homepagehttps://www.bouncycastle.org/csharp
docs_sitehttps://www.bouncycastle.org/csharp
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

63Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 20 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 27 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated11
scorecard_versionv5.5.0
checks_inconclusive7
scorecard_aggregate5.4
Excluded from scoring (no data or not applicable): Branch-Protection, CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages23
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 23 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

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.

71Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
24/40Legible commit history — 45 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.45
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes10,051
How it's scored
12.6/18One-command bootstrap — crypto/src/BouncyCastle.Crypto.csproj, crypto/test/BouncyCastle.Crypto.Tests.csproj (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — C# (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestscrypto/src/BouncyCastle.Crypto.csproj, crypto/test/BouncyCastle.Crypto.Tests.csproj
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — C# (statically typed)
54.2/55Manageable file sizes — 44/2,869 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes2,521,100
source_files_sampled2,869
oversized_source_files44
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

1,930GitHub stars
43contributors
747commits, last 12 months
23days since last push
2releases
1bus factor
113open issues
—package ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 609 ⇿
0Stars
609Forks
2Releases

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.

010020030040050060053772013-072020-022026-10
Major 0Minor 1Patch 0

Each point covers 13 days.

OpenSSF Scorecard 5.4 / 10
5.4aggregate

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).Scorecard v5.5.0 · 2026-10-20 03:14 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal 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/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 20 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 27 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
NuGetMicrosoft.NETFramework.ReferenceAssemblies1.0.3crypto/src/BouncyCastle.Crypto.csproj
NuGetMicrosoft.SourceLink.GitHub8.0.0crypto/src/BouncyCastle.Crypto.csproj
NuGetNerdbank.GitVersioning3.9.50crypto/src/BouncyCastle.Crypto.csproj
All dependencies 23

Full resolved dependency set from the GitHub dependency graph: 3 direct and 20 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
NuGetMicrosoft.NETFramework.ReferenceAssemblies1.0.3direct
NuGetMicrosoft.SourceLink.GitHub8.0.0direct
NuGetNerdbank.GitVersioning3.9.50direct
NuGetMicrosoft.NET.Test.Sdk17.13.0indirect
NuGetNUnit2.6.4indirect
NuGetNUnit3.14.0indirect
NuGetNUnit3TestAdapter5.2.0indirect
NuGetNUnitTestAdapter2.0.0indirect
NuGetSystem.Collections4.0.10indirect
NuGetSystem.Diagnostics.Debug4.0.10indirect
NuGetSystem.Globalization4.0.10indirect
NuGetSystem.IO4.0.10indirect
NuGetSystem.IO.FileSystem4.0.0indirect
NuGetSystem.IO.FileSystem.Primitives4.0.0indirect
NuGetSystem.Linq4.0.0indirect
NuGetSystem.Net.Primitives4.0.10indirect
NuGetSystem.Reflection4.0.10indirect
NuGetSystem.Reflection.Extensions4.0.0indirect
NuGetSystem.Runtime4.0.20indirect
NuGetSystem.Runtime.Extensions4.0.10indirect
NuGetSystem.Text.Encoding4.0.10indirect
NuGetSystem.Threading4.0.10indirect
NuGetSystem.Threading.Tasks4.0.10indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 23 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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.

The message is kept through sign-in.

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 — NuGet.