Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 02:25 UTC

SixLabors / ImageSharp

A modern, cross-platform, 2D Graphics library for .NET

C#Custom license★ 8,034 stars⑂ 894 forkssince Oct 2016View on GitHub ↗

SixLabors/ImageSharp holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Vitality (94/100) and lowest on Security (45/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

34
overall / 100
At Risk

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.

34
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 77 is calibrated to 91 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 50% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

Six LaborsOrganization · verified domain
257 followers26 public repossince Jan 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetSixLabors.ImageSharp4.1.1-397 days agoimageresizecropgifjpgjpegbitmappbmpngtgatiffwebpnetcore

Metrics by category

Vitality

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

94Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
31.2/36Commit cadence45/52 weeks with commits
18/18Commit volume512 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year512
human_commit_share0.99
days_since_last_push3
active_weeks_last_year45
How it's scored
27/27Ships releases49 releases published
36/36Release recencylatest release 7 days ago
19.8/27Release cadencea release every ~49.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count49
latest_release_tagv4.1.1
releases_from_tagsno
days_since_latest_release7
mean_days_between_releases49.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?

94Exceptional · 17% of overall
How it's scored
60/60Stars8,034 stars
24.6/25Forks894 forks
12.5/15Watchers176 watchers
Inputs used
forks894
stars8,034
watchers176
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
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_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescodecov.io, shields.io
has_pull_request_templateyes
How it's scored
80/80Total downloads301,431,845 downloads all-time across nuget
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesSixLabors.ImageSharp
dependents
ecosystemsnuget
total_downloads301,431,845
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?

77Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.7/22.5Commit distributiontop contributor authored 52% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 38 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled99
top_contributor_share0.524
How it's scored
41.5/42Issue resolution99% of issues closed
27.3/30PR acceptance1,329/1,461 decided PRs merged
9.3/13Newcomer PR acceptance5/7 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 8/13 approved changesets -- score normalized to 6
Inputs used
merged_prs1,329
open_issues13
closed_issues984
prs_merged_7d6
prs_decided_7d7
prs_merged_30d16
prs_decided_30d19
issue_closed_ratio0.987
closed_unmerged_prs132
first_time_authors_30d1
first_time_prs_merged_30d5
first_time_prs_decided_30d7
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
17.3/25Owner reach257 followers of SixLabors
22.4/25Track record26 public repos, account ~9 yr old
Inputs used
followers257
owner_typeOrganization
is_verifiedyes
owner_loginSixLabors
public_repos26
account_age_days3,507

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on nuget
35/35Publish recencylatest publish 7 days ago
20/20Version history39 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesSixLabors.ImageSharp
ecosystemsnuget
any_deprecatedno
min_days_since_publish7

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests8 out of 12 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://sixlabors.com/products/imagesharp/
10/10Repository description
10/10Topics13 topics
10/10Wiki
Inputs used
topicsimage-processing, drawing, c-sharp, jpeg, gif, bmp, png, netcore, exif, graphics, hacktoberfest, webp, tiff
has_wikiyes
homepagehttps://sixlabors.com/products/imagesharp/
docs_sitehttps://sixlabors.com/products/imagesharp/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

45Weak · 16% of overall
How it's scored
5.2/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionno data
1.5/2.5CI-Tests8 out of 12 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 8/13 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 38 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.2/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
2/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/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_aggregate6.2
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier50
security_posture_after_multiplier31
security_posture_before_jurisdiction62
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 50% multiplier and gives Security posture an At risk ceiling of 34.

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_packages8
unassessed_packages12
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 8 resolved dependencies against OSV. 12 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.github/copilot-instructions.md, AGENTS.md, CLAUDE.md, GEMINI.md
0/15Machine-readable docs (llms.txt)
30.2/40Legible commit history56 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.566
agent_instruction_files.github/copilot-instructions.md, AGENTS.md, CLAUDE.md, GEMINI.md
agent_instruction_max_bytes4,564
How it's scored
12.6/18One-command bootstrapsrc/ImageSharp/ImageSharp.csproj, tests/ImageSharp.Benchmarks/ImageSharp.Benchmarks.csproj, tests/ImageSharp.PublicApi.Tests/ImageSharp.PublicApi.Tests.csproj (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
0/10Reproducible environment
4/10Demonstrated agent practice2 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.02
toolchain_manifestssrc/ImageSharp/ImageSharp.csproj, tests/ImageSharp.Benchmarks/ImageSharp.Benchmarks.csproj, tests/ImageSharp.PublicApi.Tests/ImageSharp.PublicApi.Tests.csproj, tests/ImageSharp.Tests.ProfilingSandbox/ImageSharp.Tests.ProfilingSandbox.csproj, tests/ImageSharp.Tests/ImageSharp.Tests.csproj
dependency_bot_commit_share0.01
How it's scored
45/45Type-checkable codeC# (statically typed)
54.6/55Manageable file sizes15/2,101 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes641,850
source_files_sampled2,101
oversized_source_files15

Key facts

8,034GitHub stars
99contributors
512commits, last 12 months
3days since last push
49releases
1bus factor
13open 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 ★ / 894 ⇿
0Stars
894Forks
47Releases

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.

02004006008001,000871152016-102021-092026-08
Major 4Minor 2Patch 31

Each point covers 9 days.

OpenSSF Scorecard 6.2 / 10
6.2aggregate

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-08-28 02:24 UTC

7Binary-Artifactsbinaries present in source code
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
6CI-Tests8 out of 12 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 8/13 approved changesets -- score normalized to 6
10Contributorsproject has 38 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 4 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
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
NuGetSystem.IO.Hashing10.0.11src/ImageSharp/ImageSharp.csproj
NuGetSystem.Numerics.Tensors10.0.11src/ImageSharp/ImageSharp.csproj
All dependencies 20

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

RegistryPackageVersionRelation
NuGetSystem.IO.Hashing10.0.11direct
NuGetSystem.Numerics.Tensors10.0.11direct
NuGetBenchmarkDotNet0.13.0indirect
NuGetBenchmarkDotNet0.15.8indirect
NuGetBenchmarkDotNet.Diagnostics.Windows0.15.8indirect
NuGetColourfulindirect
NuGetCommandLineParser2.9.1indirect
NuGetMagick.NET-Q16-AnyCPUindirect
NuGetMicrosoft.DotNet.RemoteExecutorindirect
NuGetMicrosoft.VisualStudio.DiagnosticsHub.BenchmarkDotNetDiagnosers18.3.36812.1indirect
NuGetMoqindirect
NuGetNetVipsindirect
NuGetNetVips.Nativeindirect
NuGetPfimindirect
NuGetPhotoSauce.MagicScalerindirect
NuGetruntime.osx.10.10-x64.CoreCompat.System.Drawingindirect
NuGetSharpZipLibindirect
NuGetSkiaSharpindirect
NuGetSystem.Drawing.Commonindirect
NuGetWacton.Unicolour6.0.0indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 8 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 12 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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.