Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 12:42 UTC

serilog / serilog-sinks-console

Write log events to System.Console as text or JSON, with ANSI theme support

C#Apache-2.0★ 278 stars⑂ 77 forkssince Mar 2016View on GitHub ↗

serilog/serilog-sinks-console holds a health index of 50 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (80/100) and lowest on Security (1/100). It was last updated 255 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

SerilogOrganization
325 followers30 public repossince Oct 2013

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

Metrics by category

Vitality

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

35Weak · 21% of overall
How it's scored
3.6/36Push recencylast push 255 days ago
1.4/36Commit cadence2/52 weeks with commits
10/18Commit volume12 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year12
human_commit_share
days_since_last_push255
active_weeks_last_year2
How it's scored
27/27Ships releases13 releases published
16.2/36Release recencylatest release 255 days ago
12.6/27Release cadencea release every ~330.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count13
latest_release_tagv6.1.1
releases_from_tagsno
days_since_latest_release255
mean_days_between_releases330.5

Community & Adoption

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

80Excellent · 17% of overall
How it's scored
39.6/60Stars278 stars
15.7/25Forks77 forks
6.8/15Watchers18 watchers
Inputs used
forks77
stars278
watchers18
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

100Exceptional
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes

Sustainability & Governance

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

68Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.3/22.5Commit distributiontop contributor authored 54% of commits
13.5/13.5Contributor breadth16 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor1
contributors_sampled16
top_contributor_share0.541
How it's scored
36.1/42Issue resolution86% of issues closed
24.4/30PR acceptance66/81 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs66
open_issues13
closed_issues79
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.859
closed_unmerged_prs15
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
18.1/25Owner reach325 followers of serilog
22.9/25Track record30 public repos, account ~12 yr old
Inputs used
followers325
owner_typeOrganization
is_verified
owner_loginserilog
public_repos30
account_age_days4,657
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
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/10Topics2 topics
0/10Wiki
Inputs used
topicsserilog-sink, serilog
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?

1Critical · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfilesno dependency manifests — not applicable
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles
manifests
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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.

49Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeC# (statically typed)
55/55Manageable file sizes0/47 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes18,686
source_files_sampled47
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplessample
Inputs used
example_dirssample
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

278GitHub stars
16contributors
12commits, last 12 months
255days since last push
13releases
1bus factor
13open issues
package ecosystems

Data collection warnings

  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

All dependencies 8

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

RegistryPackageVersionRelation
NuGetMicrosoft.NET.Test.Sdk17.3.2indirect
NuGetNullable1.3.1indirect
NuGetPublicApiGenerator11.0.0indirect
NuGetSerilog4.0.0indirect
NuGetShouldly4.1.0indirect
NuGetSystem.ValueTuple4.5.0indirect
NuGetxunit2.4.1indirect
NuGetxunit.runner.visualstudio2.4.3indirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics.