Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 16:28 UTC

signalfx / splunk-otel-dotnet

Splunk Distribution of OpenTelemetry .NET

C#Apache-2.0★ 10 stars⑂ 14 forkssince Mar 2021View on GitHub ↗

signalfx/splunk-otel-dotnet holds a health index of 91 out of 100, placing it in the Excellent band. It scores highest on Vitality (93/100) and lowest on Community & Adoption (59/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

91
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).

Ownership

SignalFxOrganization
123 followers315 public repossince Jul 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetSplunk.OpenTelemetry.AutoInstrumentation1.14.0-2142 days agoopentelemetryotelapmtracingprofilinginstrumentationsplunk

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 recency — last push 1 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 205 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year205
human_commit_share0.36
days_since_last_push1
active_weeks_last_year43
How it's scored
27/27Ships releases — 26 releases published
36/36Release recency — latest release 53 days ago
19.8/27Release cadence — a release every ~68.4 days
8/10OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count26
latest_release_tagv1.15.0
releases_from_tagsno
days_since_latest_release53
mean_days_between_releases68.4

Community & Adoption

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

59Moderate · 17% of overall
How it's scored
15.5/60Stars — 10 stars
9.3/25Forks — 14 forks
5.3/15Watchers — 10 watchers
Inputs used
forks14
stars10
watchers10
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
55.5/80Total downloads — 220,451 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesSplunk.OpenTelemetry.AutoInstrumentation
dependents—
ecosystemsnuget
total_downloads220,451
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?

69Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.6/22.5Commit distribution — top contributor authored 62% of commits
13.5/13.5Contributor breadth — 12 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled12
top_contributor_share0.62
How it's scored
32.7/42Issue resolution — 78% of issues closed
25.8/30PR acceptance — 779/906 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs779
open_issues2
closed_issues7
prs_merged_7d3
prs_decided_7d3
prs_merged_30d8
prs_decided_30d8
issue_closed_ratio0.778
closed_unmerged_prs127
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
0/20Verified domain
15.1/25Owner reach — 123 followers of signalfx
25/25Track record — 315 public repos, account ~12 yr old
Inputs used
followers123
owner_typeOrganization
is_verifiedno
owner_loginsignalfx
public_repos315
account_age_days4,440
How it's scored
25/25Published & resolvable — 1 package(s) on nuget
35/35Publish recency — latest publish 142 days ago
12/20Version history — 2 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesSplunk.OpenTelemetry.AutoInstrumentation
ecosystemsnuget
any_deprecatedno
min_days_since_publish142

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://docs.splunk.com/Observability/gdi/get-data-in/application/otel-dotnet/get-started.html
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicsdotnet, instrumentation, metrics, opentelemetry, tracing
has_wikino
homepagehttps://docs.splunk.com/Observability/gdi/get-data-in/application/otel-dotnet/get-started.html
docs_sitehttps://docs.splunk.com/Observability/gdi/get-data-in/application/otel-dotnet/get-started.html
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

82Excellent · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
6/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 6 contributing companies or organizations
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 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policy — security policy file detected
6/7.5Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate7.8

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages25
unassessed_packages1
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 25 resolved dependencies against OSV. 1 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.

77Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 32 of 36 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.889
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes4,599
How it's scored
12.6/18One-command bootstrap — build/_build.csproj, src/Splunk.OpenTelemetry.AutoInstrumentation/Splunk.OpenTelemetry.AutoInstrumentation.csproj, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests.csproj (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — C# (statically typed)
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 64 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsbuild/_build.csproj, src/Splunk.OpenTelemetry.AutoInstrumentation/Splunk.OpenTelemetry.AutoInstrumentation.csproj, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests.csproj, test/Splunk.OpenTelemetry.AutoInstrumentation.Tests/Splunk.OpenTelemetry.AutoInstrumentation.Tests.csproj, test/test-applications/integrations/TestApplication.ContinuousProfiler/TestApplication.ContinuousProfiler.csproj, test/test-applications/integrations/TestApplication.HttpServer/TestApplication.HttpServer.csproj, test/test-applications/integrations/TestApplication.Smoke/TestApplication.Smoke.csproj, test/test-applications/integrations/TestApplication.Snapshots/TestApplication.Snapshots.csproj, test/test-applications/integrations/dependency-libs/TestApplication.Shared/TestApplication.Shared.csproj, test/test-applications/nuget-package/TestApplication.SelfContained/TestApplication.SelfContained.csproj, tools/MatrixHelper/MatrixHelper.csproj
dependency_bot_commit_share0.64
How it's scored
45/45Type-checkable code — C# (statically typed)
54.4/55Manageable file sizes — 3/291 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes94,684
source_files_sampled291
oversized_source_files3
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/collector/logs/v1/logs_service.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/collector/metrics/v1/metrics_service.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/collector/trace/v1/trace_service.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/common/v1/common.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/logs/v1/logs.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/metrics/v1/metrics.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/opamp/anyvalue.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/opamp/opamp.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/resource/v1/resource.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/trace/v1/trace.proto
0/20MCP server — not applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalno
api_schema_filestest/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/collector/logs/v1/logs_service.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/collector/metrics/v1/metrics_service.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/collector/trace/v1/trace_service.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/common/v1/common.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/logs/v1/logs.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/metrics/v1/metrics.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/opamp/anyvalue.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/opamp/opamp.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/resource/v1/resource.proto, test/Splunk.OpenTelemetry.AutoInstrumentation.IntegrationTests/opentelemetry/proto/trace/v1/trace.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

10GitHub stars
12contributors
205commits, last 12 months
1days since last push
26releases
1bus factor
2open issues
NuGetpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-05-12: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 10 stars today.

More detail

Star and fork history 10 ★ / 14 ⇿
10Stars
14Forks
26Releases

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.

Star history is shown as collected on 2026-05-12. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

0358101315101422022-082024-082026-07
Major 0Minor 15Patch 2

Each point covers 4 days.

OpenSSF Scorecard 7.8 / 10
7.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-12 16:27 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 6 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
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
9Security-Policysecurity policy file detected
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 14
RegistryPackageVersion constraintManifest
NuGetNuke.Common10.1.0build/_build.csproj
NuGetSystem.Security.Cryptography.Xml10.0.10build/_build.csproj
NuGetNuGet.Packaging7.9.0build/_build.csproj
NuGetMinVer8.0.0build/_build.csproj
NuGetDotNet.ReproducibleBuilds2.0.5src/Splunk.OpenTelemetry.AutoInstrumentation/Splunk.OpenTelemetry.AutoInstrumentation.csproj
NuGetMinVer8.0.0src/Splunk.OpenTelemetry.AutoInstrumentation/Splunk.OpenTelemetry.AutoInstrumentation.csproj
NuGetOpenTelemetry.Api1.16.0src/Splunk.OpenTelemetry.AutoInstrumentation/Splunk.OpenTelemetry.AutoInstrumentation.csproj
NuGetOpenTelemetry.Exporter.OpenTelemetryProtocol1.16.0src/Splunk.OpenTelemetry.AutoInstrumentation/Splunk.OpenTelemetry.AutoInstrumentation.csproj
NuGetOpenTelemetry.OpAmp.Client0.6.0-alpha.1src/Splunk.OpenTelemetry.AutoInstrumentation/Splunk.OpenTelemetry.AutoInstrumentation.csproj
NuGetOpenTelemetry.Instrumentation.AspNet1.16.0src/Splunk.OpenTelemetry.AutoInstrumentation/Splunk.OpenTelemetry.AutoInstrumentation.csproj
NuGetOpenTelemetry.Instrumentation.AspNetCore1.16.0src/Splunk.OpenTelemetry.AutoInstrumentation/Splunk.OpenTelemetry.AutoInstrumentation.csproj
NuGetOpenTelemetry.AutoInstrumentation1.16.0src/Splunk.OpenTelemetry.AutoInstrumentation/Splunk.OpenTelemetry.AutoInstrumentation.csproj
NuGetYamlDotNet18.1.0tools/MatrixHelper/MatrixHelper.csproj
NuGetMinVer8.0.0tools/MatrixHelper/MatrixHelper.csproj
All dependencies 26

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

RegistryPackageVersionRelation
NuGetDotNet.ReproducibleBuilds2.0.5direct
NuGetMinVer8.0.0direct
NuGetNuGet.Packaging7.9.0direct
NuGetNuke.Common10.1.0direct
NuGetOpenTelemetry.Api1.16.0direct
NuGetOpenTelemetry.AutoInstrumentation1.16.0direct
NuGetOpenTelemetry.Exporter.OpenTelemetryProtocol1.16.0direct
NuGetOpenTelemetry.Instrumentation.AspNet1.16.0direct
NuGetOpenTelemetry.Instrumentation.AspNetCore1.16.0direct
NuGetOpenTelemetry.OpAmp.Client0.6.0-alpha.1direct
NuGetSystem.Security.Cryptography.Xml10.0.10direct
NuGetYamlDotNet18.1.0direct
NuGetGoogle.Protobuf3.36.1indirect
NuGetGrpc.Tools2.83.0indirect
NuGetMicrosoft.Extensions.Configuration.EnvironmentVariables10.0.9indirect
NuGetMicrosoft.Extensions.Logging10.0.9indirect
NuGetMicrosoft.Extensions.Logging.Abstractions10.0.9indirect
NuGetMicrosoft.Extensions.Logging.Console10.0.9indirect
NuGetNewtonsoft.Json13.0.4indirect
NuGetSplunk.OpenTelemetry.AutoInstrumentation—indirect
NuGetSplunk.OpenTelemetry.AutoInstrumentation1.15.0indirect
NuGetSystem.Collections.Immutable10.0.9indirect
NuGetSystem.Diagnostics.DiagnosticSource10.0.9indirect
NuGetSystem.ValueTuple4.6.2indirect
NuGetTestcontainers4.15.0indirect
NuGetVerify.Xunit31.12.5indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 25 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 1 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 statistics — NuGet.