Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-01 07:35 UTC

intility / Intility.Logging

Logging packages supporting the starter templates

C#No license detected★ 14 stars⑂ 0 forkssince Jun 2021View on GitHub ↗

intility/Intility.Logging holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Vitality (80/100) and lowest on Community & Adoption (38/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

IntilityOrganization · verified domain
180 followers34 public repossince Jan 2018

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

Package ecosystems

Metrics by category

Vitality

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

80Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
10.4/36Commit cadence15/52 weeks with commits
15.1/18Commit volume47 commits in the last year
10/10OpenSSF Scorecard: Maintained22 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year47
human_commit_share0.42
days_since_last_push0
active_weeks_last_year15
How it's scored
27/27Ships releases17 releases published
36/36Release recencylatest release 0 days ago
19.8/27Release cadencea release every ~61.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count17
latest_release_tagv3.1.7
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases61.5
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?

38Weak · 17% of overall
How it's scored
18.1/60Stars14 stars
0/25Forks0 forks
3.9/15Watchers6 watchers
Inputs used
forks0
stars14
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno 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_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
64/80Total downloads1,438,674 downloads all-time across nuget
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesIntility.Extensions.Logging, Intility.Logging.AspNetCore, Intility.Extensions.Logging.Sentry, Intility.Extensions.Logging.Elasticsearch
dependents
ecosystemsnuget
total_downloads1,438,674
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?

74Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.9/22.5Commit distributiontop contributor authored 43% of commits
5.4/13.5Contributor breadth4 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor2
contributors_sampled4
top_contributor_share0.427
How it's scored
42/42Issue resolution100% of issues closed
17/30PR acceptance112/198 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/2 approved changesets -- score normalized to 0
Inputs used
merged_prs112
open_issues0
closed_issues4
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs86
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 backingorganization-owned
20/20Verified domain
16.2/25Owner reach180 followers of intility
23.2/25Track record34 public repos, account ~8 yr old
Inputs used
followers180
owner_typeOrganization
is_verifiedyes
owner_loginintility
public_repos34
account_age_days3,158

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable4 package(s) on nuget
35/35Publish recencylatest publish 0 days ago
20/20Version history31 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesIntility.Extensions.Logging, Intility.Logging.AspNetCore, Intility.Extensions.Logging.Sentry, Intility.Extensions.Logging.Elasticsearch
ecosystemsnuget
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests16 out of 22 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_ciyes
has_testsyes
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/10Topics1 topics
10/10Wiki
Inputs used
topicsdotnet
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?

75Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
1.8/2.5CI-Tests16 out of 22 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/2 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
7.5/7.5Maintained22 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
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not 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_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.8
Excluded from scoring (no data or not applicable): 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_packages18
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 18 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.

70Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history42 of 42 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapsamples/MinimalApiSample/MinimalApiSample.csproj, samples/WebSample/WebSample.csproj, samples/WorkerSample/WorkerSample.csproj (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
0/10Reproducible environment
10/10Demonstrated agent practice7 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance49 of the last 100 commits are automated dependency updates
6/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.07
toolchain_manifestssamples/MinimalApiSample/MinimalApiSample.csproj, samples/WebSample/WebSample.csproj, samples/WorkerSample/WorkerSample.csproj, src/Intility.Extensions.Logging.Elasticsearch/Intility.Extensions.Logging.Elasticsearch.csproj, src/Intility.Extensions.Logging.Sentry/Intility.Extensions.Logging.Sentry.csproj, src/Intility.Extensions.Logging/Intility.Extensions.Logging.csproj, src/Intility.Logging.AspNetCore/Intility.Logging.AspNetCore.csproj, tests/Intility.Logging.Tests/Intility.Logging.Tests.csproj
dependency_bot_commit_share0.49
How it's scored
45/45Type-checkable codeC# (statically typed)
55/55Manageable file sizes0/19 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes19,366
source_files_sampled19
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 examplessamples
Inputs used
example_dirssamples
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

14GitHub stars
4contributors
47commits, last 12 months
0days since last push
17releases
2bus factor
0open issues
package ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 6.8 / 10
6.8aggregate

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-01 07:35 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
7CI-Tests16 out of 22 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/2 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
0Licenselicense file not detected
10Maintained22 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
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 13
RegistryPackageVersion constraintManifest
NuGetElastic.Serilog.Sinks9.0.0src/Intility.Extensions.Logging.Elasticsearch/Intility.Extensions.Logging.Elasticsearch.csproj
NuGetSentry.AspNetCore6.9.0src/Intility.Extensions.Logging.Sentry/Intility.Extensions.Logging.Sentry.csproj
NuGetSentry.Serilog6.9.0src/Intility.Extensions.Logging.Sentry/Intility.Extensions.Logging.Sentry.csproj
NuGetSerilog4.4.0src/Intility.Extensions.Logging/Intility.Extensions.Logging.csproj
NuGetMicrosoft.Extensions.Hosting.Abstractions10.0.11src/Intility.Extensions.Logging/Intility.Extensions.Logging.csproj
NuGetSerilog.Enrichers.AssemblyName2.0.0src/Intility.Logging.AspNetCore/Intility.Logging.AspNetCore.csproj
NuGetSerilog.Enrichers.Environment3.0.1src/Intility.Logging.AspNetCore/Intility.Logging.AspNetCore.csproj
NuGetSerilog.Enrichers.Memory1.0.4src/Intility.Logging.AspNetCore/Intility.Logging.AspNetCore.csproj
NuGetSerilog.Enrichers.AzureClaims1.2.9src/Intility.Logging.AspNetCore/Intility.Logging.AspNetCore.csproj
NuGetMicrosoft.Extensions.Hosting.Abstractions10.0.11src/Intility.Logging.AspNetCore/Intility.Logging.AspNetCore.csproj
NuGetMicrosoft.Extensions.Logging.Abstractions10.0.11src/Intility.Logging.AspNetCore/Intility.Logging.AspNetCore.csproj
NuGetSerilog.AspNetCore10.0.0src/Intility.Logging.AspNetCore/Intility.Logging.AspNetCore.csproj
NuGetSystem.Security.Cryptography.Xml10.0.11src/Intility.Logging.AspNetCore/Intility.Logging.AspNetCore.csproj
All dependencies 18

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

RegistryPackageVersionRelation
NuGetElastic.Serilog.Sinks9.0.0direct
NuGetMicrosoft.Extensions.Hosting.Abstractions10.0.11direct
NuGetMicrosoft.Extensions.Logging.Abstractions10.0.11direct
NuGetSentry.AspNetCore6.9.0direct
NuGetSentry.Serilog6.9.0direct
NuGetSerilog4.4.0direct
NuGetSerilog.AspNetCore10.0.0direct
NuGetSerilog.Enrichers.AssemblyName2.0.0direct
NuGetSerilog.Enrichers.AzureClaims1.2.9direct
NuGetSerilog.Enrichers.Environment3.0.1direct
NuGetSerilog.Enrichers.Memory1.0.4direct
NuGetSystem.Security.Cryptography.Xml10.0.11direct
NuGetcoverlet.collector10.0.1indirect
NuGetMicrosoft.Extensions.Hosting10.0.11indirect
NuGetMicrosoft.NET.Test.Sdk18.9.0indirect
NuGetSwashbuckle.AspNetCore10.2.3indirect
NuGetxunit2.9.3indirect
NuGetxunit.runner.visualstudio4.0.0indirect
Dependency advisories 0

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