Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-29 01:22 UTC

manybrain / mailinator-csharp-client

C#No license detected★ 6 stars⑂ 1 forksince Sep 2020View on GitHub ↗

manybrain/mailinator-csharp-client holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on Vitality (68/100) and lowest on Community & Adoption (31/100). It was last updated today. 2 contributors account for most of its recent work.

51
overall / 100
Moderate

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.

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

Ownership

Manybrain, LLCPersonal account
3 followers12 public repossince Oct 2015Manybrain, LLC

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetMailinatorApiClient2.0.0-90 days agomanybrainapiclient

Metrics by category

Vitality

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

68Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
5.5/36Commit cadence — 8/52 weeks with commits
14.3/18Commit volume — 38 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year38
human_commit_share0.964
days_since_last_push0
active_weeks_last_year8
How it's scored
16.2/27Ships releases — 1 version tags (no GitHub releases)
36/36Release recency — latest release 0 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv2.0.0
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases—
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?

31At Risk · 17% of overall
How it's scored
11.3/60Stars — 6 stars
0/25Forks — 1 forks
0/15Watchers — 2 watchers
Inputs used
forks1
stars6
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
58.6/80Total downloads — 433,563 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesMailinatorApiClient
dependents—
ecosystemsnuget
total_downloads433,563
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?

66Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.2/22.5Commit distribution — top contributor authored 42% of commits
5.4/13.5Contributor breadth — 4 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor2
contributors_sampled4
top_contributor_share0.415
How it's scored
42/42Issue resolution — 100% of issues closed
24/30PR acceptance — 4/5 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/4 approved changesets -- score normalized to 0
Inputs used
merged_prs4
open_issues0
closed_issues1
prs_merged_7d2
prs_decided_7d3
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio1
closed_unmerged_prs1
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
4.3/25Owner reach — 3 followers of manybrain
20.1/25Track record — 12 public repos, account ~10 yr old
Inputs used
followers3
owner_typeUser
is_verified—
owner_loginmanybrain
public_repos12
account_age_days3,986
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

33At Risk · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests — 1 out of 4 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

44Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0.5/2.5CI-Tests — 1 out of 4 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/4 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

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.

66Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://www.mailinator.com/llms.txt)
6/40Legible commit history — 6 of 53 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://www.mailinator.com/llms.txt
legible_history_share0.113
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes2,411
How it's scored
12.6/18One-command bootstrap — eng/OpenApiCoverageCheck/OpenApiCoverageCheck.csproj, mailinator-csharp-client-tests/mailinator-csharp-client-tests.csproj, mailinator-csharp-client-unit-tests/mailinator-csharp-client-unit-tests.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — C# (statically typed)
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 3 of the last 55 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsno
lockfilespackages.lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.055
toolchain_manifestseng/OpenApiCoverageCheck/OpenApiCoverageCheck.csproj, mailinator-csharp-client-tests/mailinator-csharp-client-tests.csproj, mailinator-csharp-client-unit-tests/mailinator-csharp-client-unit-tests.csproj, mailinator-csharp-client/mailinator-csharp-client.csproj
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — C# (statically typed)
55/55Manageable file sizes — 0/164 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes26,697
source_files_sampled164
oversized_source_files0

Key facts

6GitHub stars
4contributors
38commits, last 12 months
0days since last push
1releases
2bus factor
0open issues
NuGetpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.4 / 10
4.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-09-29 01:21 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
2CI-Tests1 out of 4 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/4 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
NuGetMicrosoft.NET.Test.Sdk18.10.1mailinator-csharp-client-tests/mailinator-csharp-client-tests.csproj
NuGetMSTest.TestAdapter4.4.1mailinator-csharp-client-tests/mailinator-csharp-client-tests.csproj
NuGetMSTest.TestFramework4.4.1mailinator-csharp-client-tests/mailinator-csharp-client-tests.csproj
NuGetMicrosoft.NET.Test.Sdk18.10.1mailinator-csharp-client-unit-tests/mailinator-csharp-client-unit-tests.csproj
NuGetMSTest.TestAdapter4.4.1mailinator-csharp-client-unit-tests/mailinator-csharp-client-unit-tests.csproj
NuGetMSTest.TestFramework4.4.1mailinator-csharp-client-unit-tests/mailinator-csharp-client-unit-tests.csproj
NuGetMicrosoft.NETFramework.ReferenceAssemblies1.0.3mailinator-csharp-client/mailinator-csharp-client.csproj
NuGetNewtonsoft.Json13.0.4mailinator-csharp-client/mailinator-csharp-client.csproj
NuGetRestSharp114.0.0mailinator-csharp-client/mailinator-csharp-client.csproj
NuGetSystem.Text.Json10.0.12mailinator-csharp-client/mailinator-csharp-client.csproj
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.