Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-15 16:50 UTC

opentelemetry-php / contrib-propagator-traceresponse

[READONLY] TraceResponse propagator contrib module

PHPNo license detected★ 1 star⑂ 0 forkssince Apr 2023View on GitHub ↗

opentelemetry-php/contrib-propagator-traceresponse holds a health index of 44 out of 100, placing it in the Weak band. It scores highest on Vitality (64/100) and lowest on Security (24/100). It was last updated today. 3 contributors account for most of its recent work.

44
overall / 100
Weak

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.

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

Ownership

38 followers82 public repossince Dec 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistopen-telemetry/opentelemetry-propagation-traceresponse0.2.027,4207113 days agoopentelemetryopen-telemetryotelpropagatortraceresponse

Metrics by category

Vitality

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

64Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
3.5/36Commit cadence5/52 weeks with commits
8.1/18Commit volume7 commits in the last year
2/10OpenSSF Scorecard: Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year7
human_commit_share
days_since_last_push0
active_weeks_last_year5
How it's scored
27/27Ships releases8 releases published
36/36Release recencylatest release 0 days ago
12.6/27Release cadencea release every ~170.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count8
latest_release_tag0.3.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases170.2
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?

26At Risk · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
1.7/15Watchers3 watchers
Inputs used
forks0
stars1
watchers3
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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
59.2/80Monthly downloads27,420 downloads/month across packagist
6/20Registry dependents7 packages depend on it
Inputs used
packagesopen-telemetry/opentelemetry-propagation-traceresponse
dependents7
ecosystemspackagist
total_downloads455,220
monthly_downloads27,420
unverified_packages_excluded

Sustainability & Governance

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

60Moderate · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
18.3/22.5Commit distributiontop contributor authored 19% of commits
13.5/13.5Contributor breadth10 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor3
contributors_sampled10
top_contributor_share0.188
How it's scored
0/42Issue resolutionno issues or no data
0/30PR acceptanceno decided pull requests or no data
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/16 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
11.4/25Owner reach38 followers of opentelemetry-php
22.1/25Track record82 public repos, account ~4 yr old
Inputs used
followers38
owner_typeOrganization
is_verified
owner_loginopentelemetry-php
public_repos82
account_age_days1,657
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 113 days ago
20/20Version history7 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesopen-telemetry/opentelemetry-propagation-traceresponse
ecosystemspackagist
any_deprecatedno
min_days_since_publish113

Engineering Quality

Are baseline engineering and documentation practices in place?

46Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config.php-cs-fixer.php
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
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?

24At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/16 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
1.5/7.5Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate2.4
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

32At Risk · 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
11/11Lint / format config.php-cs-fixer.php
0/11Static type checking
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_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/4 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes4,123
source_files_sampled4
oversized_source_files0

Key facts

1GitHub stars
10contributors
7commits, last 12 months
0days since last push
8releases
3bus factor
0open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 2.4 / 10
2.4aggregate

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-07-15 16:50 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/16 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
2Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
Packagistopen-telemetry/context^1.4composer.json
All dependencies 14

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

RegistryPackageVersionRelation
Packagistopen-telemetry/contextdirect
Packagistfriendsofphp/php-cs-fixerindirect
Packagistguzzlehttp/promisesindirect
Packagistnyholm/psr7indirect
Packagistopen-telemetry/sdkindirect
Packagistphan/phanindirect
Packagistphpindirect
Packagistphp-http/message-factoryindirect
Packagistphpstan/phpstanindirect
Packagistphpstan/phpstan-phpunitindirect
Packagistphpunit/phpunitindirect
Packagistpsalm/plugin-phpunitindirect
Packagistsymfony/http-clientindirect
Packagistvimeo/psalm6.4.0indirect
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 statisticsPackagist.