Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 23:53 UTC

devlooped / chromium

Run a portable Chromium using dotnet 8+ and nuget.

C#MIT★ 15 stars⑂ 2 forkssince Jun 2022View on GitHub ↗
KindCommand-line toolhow this is determined

devlooped/chromium holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (90/100) and lowest on Engineering Quality (50/100). It was last updated today. A single contributor accounts for most of its recent work.

73
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.

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

Ownership

devloopedOrganization · verified domain
137 followers114 public repossince Feb 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
NuGetchromium2026.9.1-5913 days ago
NuGetdotnet-chromium2026.9.1-5813 days ago

Metrics by category

Vitality

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

90Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
20.8/36Commit cadence — 30/52 weeks with commits
16.2/18Commit volume — 63 commits in the last year
10/10OpenSSF Scorecard: Maintained — 16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year63
human_commit_share0.83
days_since_last_push0
active_weeks_last_year30

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 90 releases published
36/36Release recency — latest release 13 days ago
27/27Release cadence — a release every ~12 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count90
latest_release_tagv2026.9.1
releases_from_tagsno
days_since_latest_release13
mean_days_between_releases12
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?

55Moderate · 17% of overall
How it's scored
18.6/60Stars — 15 stars
0/25Forks — 2 forks
0/15Watchers — 1 watchers
Inputs used
forks2
stars15
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges9
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
57.9/80Total downloads — 373,706 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageschromium, dotnet-chromium
dependents—
ecosystemsnuget
total_downloads373,706
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.5/22.5Commit distribution — top contributor authored 58% of commits
2.7/13.5Contributor breadth — 2 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.576
How it's scored
36/42Issue resolution — 86% of issues closed
5.4/30PR acceptance — 77/429 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/21 approved changesets -- score normalized to 0
Inputs used
merged_prs77
open_issues1
closed_issues6
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.857
closed_unmerged_prs352
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
30/30Ownership backing — organization-owned
20/20Verified domain
15.4/25Owner reach — 137 followers of devlooped
25/25Track record — 114 public repos, account ~6 yr old
Inputs used
followers137
owner_typeOrganization
is_verifiedyes
owner_logindevlooped
public_repos114
account_age_days2,391

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on nuget
35/35Publish recency — latest publish 13 days ago
20/20Version history — 59 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageschromium, dotnet-chromium
ecosystemsnuget
any_deprecatedno
min_days_since_publish13

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 2 topics
0/10Wiki
Inputs used
topicschromium, playwright
has_wikino
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?

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
2.5/2.5CI-Tests — 15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/21 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file 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_aggregate6.3
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

53Moderate · 4% of overall
How it's scored
45/45Agent instructions — .github/copilot-instructions.md
0/15Machine-readable docs (llms.txt)
10.3/40Legible commit history — 16 of 83 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.193
agent_instruction_files.github/copilot-instructions.md
agent_instruction_max_bytes4,203
How it's scored
12.6/18One-command bootstrap — src/CodeAnalysis/CodeAnalysis.csproj, src/chromium/chromium.csproj, src/dotnet-chromium/dotnet-chromium.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — C# (statically typed)
0/10Reproducible environment
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 9 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.01
toolchain_manifestssrc/CodeAnalysis/CodeAnalysis.csproj, src/chromium/chromium.csproj, src/dotnet-chromium/dotnet-chromium.csproj
dependency_bot_commit_share0.09
How it's scored
45/45Type-checkable code — C# (statically typed)
55/55Manageable file sizes — 0/5 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes4,521
source_files_sampled5
oversized_source_files0

Key facts

15GitHub stars
2contributors
63commits, last 12 months
0days since last push
90releases
1bus factor
1open issues
—package ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

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

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.

111222212024-082024-102024-12
Major 0Minor 0Patch 10
OpenSSF Scorecard 6.3 / 10
6.3aggregate

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-14 23:53 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-Tests15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/21 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 15
RegistryPackageVersion constraintManifest
NuGetNuGetizer—src/CodeAnalysis/CodeAnalysis.csproj
NuGetMicrosoft.CodeAnalysis.CSharp—src/CodeAnalysis/CodeAnalysis.csproj
NuGetDevlooped.SponsorLink—src/CodeAnalysis/CodeAnalysis.csproj
NuGetThisAssembly.Project—src/CodeAnalysis/CodeAnalysis.csproj
NuGetNuGetizer—src/chromium/chromium.csproj
NuGetMicrosoft.Extensions.DependencyModel—src/chromium/chromium.csproj
NuGetNuGet.ProjectModel—src/chromium/chromium.csproj
NuGetNuGetizer—src/dotnet-chromium/dotnet-chromium.csproj
NuGetMicrosoft.Extensions.DependencyModel—src/dotnet-chromium/dotnet-chromium.csproj
NuGetMicrosoft.Playwright—src/dotnet-chromium/dotnet-chromium.csproj
NuGetSpectre.Console—src/dotnet-chromium/dotnet-chromium.csproj
NuGetThisAssembly.Project—src/dotnet-chromium/dotnet-chromium.csproj
NuGetchromium.linux-x64—src/dotnet-chromium/dotnet-chromium.csproj
NuGetchromium.win-x64—src/dotnet-chromium/dotnet-chromium.csproj
NuGetchromium.win-x86—src/dotnet-chromium/dotnet-chromium.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
NuGetchromium.linux-x64—direct
NuGetchromium.win-x64—direct
NuGetchromium.win-x86—direct
NuGetDevlooped.SponsorLink—direct
NuGetMicrosoft.CodeAnalysis.CSharp—direct
NuGetMicrosoft.Extensions.DependencyModel—direct
NuGetMicrosoft.Playwright—direct
NuGetNuGet.ProjectModel—direct
NuGetNuGetizer—direct
NuGetSpectre.Console—direct
NuGetThisAssembly.Project—direct
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.