Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 11:33 UTC

Adyen / adyen-dotnet-api-library

Adyen API Library for .NET

C#MIT★ 127 stars⑂ 123 forkssince Nov 2017View on GitHub ↗

Adyen/adyen-dotnet-api-library holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on Vitality (93/100) and lowest on Engineering Quality (50/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

92
overall / 100
Excellent

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.

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

Ownership

AdyenOrganization · verified domain
537 followers66 public repossince Nov 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetAdyen36.0.0-953 days ago36.0.0

Metrics by category

Vitality

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

93Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
23.5/36Commit cadence34/52 weeks with commits
18/18Commit volume733 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year733
human_commit_share1
days_since_last_push1
active_weeks_last_year34

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 3 days ago
27/27Release cadencea release every ~23.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv36.0.0
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases23.1
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?

77Good · 17% of overall
How it's scored
34.1/60Stars127 stars
17.4/25Forks123 forks
5.8/15Watchers12 watchers
Inputs used
forks123
stars127
watchers12
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
70.1/80Total downloads5,550,841 downloads all-time across nuget
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesAdyen
dependents
ecosystemsnuget
total_downloads5,550,841
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?

86Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
15.9/22.5Commit distributiontop contributor authored 29% of commits
13.5/13.5Contributor breadth68 contributors
10/10OpenSSF Scorecard: Contributorsproject has 22 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled68
top_contributor_share0.293
How it's scored
40/42Issue resolution95% of issues closed
24.6/30PR acceptance1,209/1,476 decided PRs merged
10.8/13Newcomer PR acceptance5/6 first-time contributors' PRs merged in 30d
13.5/15OpenSSF Scorecard: Code-ReviewFound 23/25 approved changesets -- score normalized to 9
Inputs used
merged_prs1,209
open_issues17
closed_issues348
prs_merged_7d2
prs_decided_7d2
prs_merged_30d27
prs_decided_30d28
issue_closed_ratio0.953
closed_unmerged_prs267
first_time_authors_30d2
first_time_prs_merged_30d5
first_time_prs_decided_30d6
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
19.6/25Owner reach537 followers of Adyen
25/25Track record66 public repos, account ~11 yr old
Inputs used
followers537
owner_typeOrganization
is_verifiedyes
owner_loginAdyen
public_repos66
account_age_days4,327

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on nuget
35/35Publish recencylatest publish 3 days ago
20/20Version history95 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesAdyen
ecosystemsnuget
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

50Moderate · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests23 out of 23 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics10 topics
10/10Wiki
Inputs used
topicsadyen, payments, api-client, api-library, payment, payment-gateway, payment-integration, dotnet, dotnetcore2, hacktoberfest
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

89Excellent · 16% of overall

Security posture

86Excellent
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests23 out of 23 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6.8/7.5Code-ReviewFound 23/25 approved changesets -- score normalized to 9
2.5/2.5Contributorsproject has 22 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
3/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
3.5/5SASTSAST tool detected but not run on all commits
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
6.8/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate8.6
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages11
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 11 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.

54Moderate · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://docs.adyen.com/llms.txt)
2.7/40Legible commit history5 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.adyen.com/llms.txt
legible_history_share0.05
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes2,415
How it's scored
12.6/18One-command bootstrapAdyen.IntegrationTest/Adyen.IntegrationTest.csproj, Adyen.Test/Adyen.Test.csproj, Adyen/Adyen.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
6/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsAdyen.IntegrationTest/Adyen.IntegrationTest.csproj, Adyen.Test/Adyen.Test.csproj, Adyen/Adyen.csproj
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeC# (statically typed)
52.6/55Manageable file sizes104/2,340 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes252,042
source_files_sampled2,340
oversized_source_files104

Key facts

127GitHub stars
68contributors
733commits, last 12 months
1days since last push
100releases
2bus factor
17open issues
NuGetpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 123 ⇿
0Stars
123Forks
98Releases

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.

02040608010012012032017-112022-032026-06
Major 32Minor 36Patch 27

Each point covers 8 days.

OpenSSF Scorecard 8.6 / 10
8.6aggregate

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-18 11:32 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
10CI-Tests23 out of 23 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
9Code-ReviewFound 23/25 approved changesets -- score normalized to 9
10Contributorsproject has 22 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
6Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
7SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 14
RegistryPackageVersion constraintManifest
NuGetMicrosoft.NET.Test.Sdk17.13.0Adyen.IntegrationTest/Adyen.IntegrationTest.csproj
NuGetMSTest.TestAdapter3.11.1Adyen.IntegrationTest/Adyen.IntegrationTest.csproj
NuGetMSTest.TestFramework3.11.1Adyen.IntegrationTest/Adyen.IntegrationTest.csproj
NuGetMicrosoft.NET.Test.Sdk17.13.0Adyen.Test/Adyen.Test.csproj
NuGetMSTest.TestAdapter3.11.1Adyen.Test/Adyen.Test.csproj
NuGetMSTest.TestFramework3.11.1Adyen.Test/Adyen.Test.csproj
NuGetNSubstitute5.3.0Adyen.Test/Adyen.Test.csproj
NuGetMicrosoft.Extensions.Hosting8.0.1Adyen/Adyen.csproj
NuGetMicrosoft.Extensions.Http8.0.1Adyen/Adyen.csproj
NuGetMicrosoft.Extensions.Http.Polly8.0.20Adyen/Adyen.csproj
NuGetNewtonsoft.Json13.0.3Adyen/Adyen.csproj
NuGetPolly8.6.4Adyen/Adyen.csproj
NuGetSystem.Text.Json8.0.6Adyen/Adyen.csproj
NuGetSystem.Net.Http4.3.4Adyen/Adyen.csproj
All dependencies 11

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

RegistryPackageVersionRelation
NuGetMicrosoft.Extensions.Hosting8.0.1direct
NuGetMicrosoft.Extensions.Http8.0.1direct
NuGetMicrosoft.Extensions.Http.Polly8.0.20direct
NuGetMicrosoft.NET.Test.Sdk17.13.0direct
NuGetMSTest.TestAdapter3.11.1direct
NuGetMSTest.TestFramework3.11.1direct
NuGetNewtonsoft.Json13.0.3direct
NuGetNSubstitute5.3.0direct
NuGetPolly8.6.4direct
NuGetSystem.Net.Http4.3.4direct
NuGetSystem.Text.Json8.0.6direct
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 11 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 statisticsNuGet.