Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 03:26 UTC

signalfx / splunk-otel-python

Splunk distribution of OpenTelemetry Python

PythonApache-2.0★ 41 stars⑂ 19 forkssince Sep 2020View on GitHub ↗
KindPluginLibraryhow this is determined

signalfx/splunk-otel-python holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (86/100) and lowest on AI Readiness (56/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

SignalFxOrganization
123 followers316 public repossince Jul 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIsplunk-opentelemetry2.13.254,355885 days ago

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
18.7/36Commit cadence — 27/52 weeks with commits
16.3/18Commit volume — 65 commits in the last year
10/10OpenSSF Scorecard: Maintained — 20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year65
human_commit_share0.88
days_since_last_push0
active_weeks_last_year27
How it's scored
27/27Ships releases — 59 releases published
36/36Release recency — latest release 5 days ago
19.8/27Release cadence — a release every ~46.3 days
8/10OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count59
latest_release_tagv2.13.2
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases46.3

Community & Adoption

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

66Good · 17% of overall
How it's scored
26/60Stars — 41 stars
10.5/25Forks — 19 forks
6/15Watchers — 13 watchers
Inputs used
forks19
stars41
watchers13
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 (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_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
63.1/80Monthly downloads — 54,355 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagessplunk-opentelemetry
dependents—
ecosystemspypi
total_downloads—
monthly_downloads54,355
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.8/22.5Commit distribution — top contributor authored 87% of commits
9.5/13.5Contributor breadth — 7 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.874
How it's scored
25/42Issue resolution — 60% of issues closed
19.1/30PR acceptance — 488/767 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_prs488
open_issues15
closed_issues22
prs_merged_7d2
prs_decided_7d2
prs_merged_30d5
prs_decided_30d6
issue_closed_ratio0.595
closed_unmerged_prs279
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 — 316 public repos, account ~12 yr old
Inputs used
followers123
owner_typeOrganization
is_verifiedno
owner_loginsignalfx
public_repos316
account_age_days4,477

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 5 days ago
20/20Version history — 88 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagessplunk-opentelemetry
ecosystemspypi
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/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_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://github.com/signalfx/splunk-otel-python#readme
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://github.com/signalfx/splunk-otel-python#readme
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

78Good · 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 3 contributing companies or organizations -- score normalized to 10
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 — 20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
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_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.2
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages34
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:splunk-opentelemetry@2.13.2 runtime dependency closure — what installing the published package pulls in — 34 packages. 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.

56Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 84 of 88 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.955
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 12 of the last 100 commits are automated dependency updates
1/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.12
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/42 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes29,783
source_files_sampled42
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
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

41GitHub stars
7contributors
65commits, last 12 months
0days since last push
59releases
1bus factor
15open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 19 ⇿
0Stars
19Forks
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.

0481216201922021-052024-012026-10
Major 2Minor 34Patch 7

Each point covers 5 days.

OpenSSF Scorecard 7.2 / 10
7.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-10-19 03:26 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 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-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
PyPIopentelemetry-api==1.45.1pyproject.toml
PyPIopentelemetry-sdk==1.45.1pyproject.toml
PyPIopentelemetry-propagator-b3==1.45.1pyproject.toml
PyPIopentelemetry-exporter-otlp-proto-grpc==1.45.1pyproject.toml
PyPIopentelemetry-exporter-otlp-proto-http==1.45.1pyproject.toml
PyPIopentelemetry-configuration==0.66b1pyproject.toml
PyPIopentelemetry-instrumentation==0.66b1pyproject.toml
PyPIopentelemetry-instrumentation-logging==0.66b1pyproject.toml
PyPIopentelemetry-instrumentation-system-metrics==0.66b1pyproject.toml
PyPIopentelemetry-semantic-conventions==0.66b1pyproject.toml
PyPIopentelemetry-opamp-client==0.4b0pyproject.toml
PyPIprotobuf>=6.33.5pyproject.toml
PyPIrequests>=2.33.0pyproject.toml
PyPIwrapt>=2.5.0pyproject.toml
All dependencies 137

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

RegistryPackageVersionRelation
PyPIopentelemetry-api1.27.0direct
PyPIopentelemetry-api1.45.1direct
PyPIopentelemetry-configuration0.66b1direct
PyPIopentelemetry-exporter-otlp-proto-grpc1.27.0direct
PyPIopentelemetry-exporter-otlp-proto-grpc1.45.1direct
PyPIopentelemetry-exporter-otlp-proto-http1.27.0direct
PyPIopentelemetry-exporter-otlp-proto-http1.45.1direct
PyPIopentelemetry-instrumentation0.48b0direct
PyPIopentelemetry-instrumentation0.66b1direct
PyPIopentelemetry-instrumentation-logging0.66b1direct
PyPIopentelemetry-instrumentation-system-metrics0.48b0direct
PyPIopentelemetry-instrumentation-system-metrics0.66b1direct
PyPIopentelemetry-opamp-client0.4b0direct
PyPIopentelemetry-propagator-b31.27.0direct
PyPIopentelemetry-propagator-b31.45.1direct
PyPIopentelemetry-sdk1.27.0direct
PyPIopentelemetry-sdk1.45.1direct
PyPIopentelemetry-semantic-conventions0.48b0direct
PyPIopentelemetry-semantic-conventions0.66b1direct
PyPIprotobuf—direct
PyPIprotobuf4.25.5direct
PyPIrequests—direct
PyPIrequests2.32.3direct
PyPIwrapt—direct
PyPIwrapt1.17.2direct
PyPIappnope—indirect
PyPIastroid2.15.8indirect
PyPIattrs24.2.0indirect
PyPIbackcall—indirect
PyPIblack24.8.0indirect
PyPIcertifi2024.8.30indirect
PyPIcffi1.17.1indirect
PyPIcharset-normalizer3.3.2indirect
PyPIclick8.1.7indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.6.1indirect
PyPIcryptography43.0.3indirect
PyPIdecorator—indirect
PyPIdeprecated1.2.14indirect
PyPIdill0.3.8indirect
PyPIexceptiongroup1.2.2indirect
PyPIfalcon2.0.0indirect
PyPIflake85.0.4indirect
PyPIgoogleapis-common-protos1.65.0indirect
PyPIgrpcio1.66.1indirect
PyPIidna3.8indirect
PyPIimportlib-metadata8.4.0indirect
PyPIiniconfig2.0.0indirect
PyPIipython—indirect
PyPIipython-genutils—indirect
PyPIisort5.13.2indirect
PyPIjedi—indirect
PyPIkeepachangelog1.0.0indirect
PyPIlazy-object-proxy1.10.0indirect
PyPImccabe0.7.0indirect
PyPImypy1.14.1indirect
PyPImypy-extensions1.0.0indirect
PyPIopentelemetry-exporter-otlp-proto-common1.27.0indirect
PyPIopentelemetry-instrumentation-aio-pika0.66b1indirect
PyPIopentelemetry-instrumentation-aiohttp-client0.66b1indirect
PyPIopentelemetry-instrumentation-aiohttp-server0.66b1indirect
PyPIopentelemetry-instrumentation-aiokafka0.66b1indirect
PyPIopentelemetry-instrumentation-aiopg0.66b1indirect
PyPIopentelemetry-instrumentation-asgi0.66b1indirect
PyPIopentelemetry-instrumentation-asyncio0.66b1indirect
PyPIopentelemetry-instrumentation-asyncpg0.66b1indirect
PyPIopentelemetry-instrumentation-aws-lambda0.66b1indirect
PyPIopentelemetry-instrumentation-boto3sqs0.66b1indirect
PyPIopentelemetry-instrumentation-botocore0.66b1indirect
PyPIopentelemetry-instrumentation-cassandra0.66b1indirect
PyPIopentelemetry-instrumentation-celery0.66b1indirect
PyPIopentelemetry-instrumentation-click0.66b1indirect
PyPIopentelemetry-instrumentation-confluent-kafka0.66b1indirect
PyPIopentelemetry-instrumentation-dbapi0.66b1indirect
PyPIopentelemetry-instrumentation-django0.66b1indirect
PyPIopentelemetry-instrumentation-falcon0.66b1indirect
PyPIopentelemetry-instrumentation-fastapi0.66b1indirect
PyPIopentelemetry-instrumentation-flask0.66b1indirect
PyPIopentelemetry-instrumentation-grpc0.66b1indirect
PyPIopentelemetry-instrumentation-httpx0.66b1indirect
PyPIopentelemetry-instrumentation-jinja20.66b1indirect
PyPIopentelemetry-instrumentation-kafka-python0.66b1indirect
PyPIopentelemetry-instrumentation-mysql0.66b1indirect
PyPIopentelemetry-instrumentation-mysqlclient0.66b1indirect
PyPIopentelemetry-instrumentation-pika0.66b1indirect
PyPIopentelemetry-instrumentation-psycopg0.66b1indirect
PyPIopentelemetry-instrumentation-psycopg20.66b1indirect
PyPIopentelemetry-instrumentation-pymemcache0.66b1indirect
PyPIopentelemetry-instrumentation-pymongo0.66b1indirect
PyPIopentelemetry-instrumentation-pymysql0.66b1indirect
PyPIopentelemetry-instrumentation-pyramid0.66b1indirect
PyPIopentelemetry-instrumentation-redis0.66b1indirect
PyPIopentelemetry-instrumentation-remoulade0.66b1indirect
PyPIopentelemetry-instrumentation-requests0.66b1indirect
PyPIopentelemetry-instrumentation-sqlalchemy0.66b1indirect
PyPIopentelemetry-instrumentation-sqlite30.66b1indirect
PyPIopentelemetry-instrumentation-starlette0.66b1indirect
PyPIopentelemetry-instrumentation-threading0.66b1indirect
PyPIopentelemetry-instrumentation-tornado0.66b1indirect
PyPIopentelemetry-instrumentation-tortoiseorm0.66b1indirect
PyPIopentelemetry-instrumentation-urllib0.66b1indirect
PyPIopentelemetry-instrumentation-urllib30.66b1indirect
PyPIopentelemetry-instrumentation-wsgi0.66b1indirect
PyPIopentelemetry-proto1.27.0indirect
PyPIpackaging24.1indirect
PyPIparso—indirect
PyPIpathspec0.12.1indirect
PyPIpexpect—indirect
PyPIpickleshare—indirect
PyPIplatformdirs4.3.2indirect
PyPIpluggy1.5.0indirect
PyPIprompt-toolkit—indirect
PyPIpsutil6.0.0indirect
PyPIptyprocess—indirect
PyPIpycodestyle2.9.1indirect
PyPIpycparser2.22indirect
PyPIpyflakes2.5.0indirect
PyPIpygments—indirect
PyPIpylint2.17.7indirect
PyPIpylintfileheader0.3.3indirect
PyPIpytest8.3.4indirect
PyPIpytest-cov5.0.0indirect
PyPIpytest-docker3.1.1indirect
PyPIrequests-futures1.0.2indirect
PyPIsecureapp-python-agent—indirect
PyPIsecureapp-python-agent26.10.0indirect
PyPIsetuptools74.1.2indirect
PyPIsplunk-opentelemetry—indirect
PyPIsplunk-opentelemetry2.13.2indirect
PyPItomli2.0.1indirect
PyPItomlkit0.13.2indirect
PyPItraitlets—indirect
PyPItypes-setuptools75.6.0.20241126indirect
PyPItyping-extensions4.12.2indirect
PyPIurllib32.2.3indirect
PyPIwcwidth—indirect
PyPIzipp3.20.1indirect
Dependency advisories 0

Installing pypi:splunk-opentelemetry@2.13.2 pulls in 34 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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 — PyPI.