Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-16 19:57 UTC

trentm / opentelemetry-js

OpenTelemetry JavaScript Client

TypeScriptApache-2.0★ 0 stars⑂ 1 forksince Apr 2022forkView on GitHub ↗
KindNetwork servicehow this is determined

trentm/opentelemetry-js holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on Vitality (79/100) and lowest on Community & Adoption (12/100). It was last updated 2 days ago. 5 contributors account for most of its recent work.

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

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

Ownership

Trent MickPersonal account
650 followers203 public repossince Jan 2009@elastic

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@opentelemetry/apipoints to another repo — not scored1.10.0528,584,6216727 days agoopentelemetrynodejsbrowsertracingprofilingstatsmonitoring
npm@opentelemetry/semantic-conventionspoints to another repo — not scored1.45.0574,882,57412710 days agoopentelemetrynodejstracingattributessemantic-conventions
npm@opentelemetry/sdk-logspoints to another repo — not scored3.1.1312,972,750687 days agoopentelemetrynodejslogsstatsprofiling
npm@opentelemetry/sdk-tracepoints to another repo — not scored3.1.1258,121,317127 days agoopentelemetrynodejstracingprofilingmetricsstats
npm@opentelemetry/sdk-metricspoints to another repo — not scored3.1.1352,543,386627 days agoopentelemetrynodejsmetricsstatsprofiling
npm@opentelemetry/corepoints to another repo — not scored3.1.1795,588,6632057 days agoopentelemetrynodejsbrowsertracingprofilingmetricsstats
npm@opentelemetry/resourcespoints to another repo — not scored3.1.1661,337,9792017 days agoopentelemetrynodejsresourcesstatsprofiling
npm@opentelemetry/context-zonepoints to another repo — not scored3.1.15,804,3771577 days agoopentelemetrywebtracingprofilingmetricsstats
npm@opentelemetry/propagator-b3points to another repo — not scored3.1.1124,624,4731517 days agoopentelemetrynodejstracingprofilingmonitoringb3
npm@opentelemetry/exporter-zipkinpoints to another repo — not scored3.1.1125,598,2962397 days agoopentelemetrynodejsbrowsertracingprofiling

Metrics by category

Vitality

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

79Good · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
35.3/36Commit cadence — 51/52 weeks with commits
18/18Commit volume — 744 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_year744
human_commit_share0.74
days_since_last_push2
active_weeks_last_year51
How it's scored
16.2/27Ships releases — 44 version tags (no GitHub releases)
0/36Release recency — latest release 1,700 days ago
27/27Release cadence — a release every ~37.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count44
latest_release_tagv1.1.1
releases_from_tagsyes
days_since_latest_release1,700
mean_days_between_releases37.1
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?

12Critical · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno

Sustainability & Governance

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

55Moderate · 23% of overall
How it's scored
45.9/54Bus factor — 5 contributor(s) cover half of all commits
19.3/22.5Commit distribution — top contributor authored 14% of commits
13.5/13.5Contributor breadth — 97 contributors
10/10OpenSSF Scorecard: Contributors — project has 41 contributing companies or organizations
Inputs used
bus_factor5
contributors_sampled97
top_contributor_share0.143
How it's scored
0/42Issue resolution — no issues or no data
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
20.2/25Owner reach — 650 followers of trentm
25/25Track record — 203 public repos, account ~17 yr old
Inputs used
followers650
owner_typeUser
is_verified—
owner_logintrentm
public_repos203
account_age_days6,514
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

69Good · 19% of overall
How it's scored
24/24CI workflows — 21 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.mjs
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
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
0/30README
25/25Documentation directory
15/15Documentation / homepage site — https://opentelemetry.io
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://opentelemetry.io
docs_sitehttps://opentelemetry.io
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 41 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
0/5Packaging — no data
4/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
5/5SAST — SAST tool detected: CodeQL
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5Vulnerabilities — 32 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. 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.

72Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://opentelemetry.io/llms.txt)
40/40Legible commit history — 74 of 74 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://opentelemetry.io/llms.txt
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.mjs
11/11Static type checking — api/tsconfig.json, bundler-tests/node/typescript-legacy/tsconfig.json, examples/dice/instrumented/tsconfig.json, examples/dice/uninstrumented/tsconfig.json, examples/esm-http-ts/tsconfig.json, experimental/examples/declarative-config/tsconfig.json, experimental/packages/api-config/tsconfig.json, experimental/packages/configuration/tsconfig.json, experimental/packages/exporter-logs-otlp-grpc/tsconfig.json, experimental/packages/exporter-logs-otlp-http/tsconfig.json, experimental/packages/exporter-logs-otlp-proto/tsconfig.json, experimental/packages/exporter-trace-otlp-grpc/tsconfig.json, experimental/packages/exporter-trace-otlp-http/tsconfig.json, experimental/packages/exporter-trace-otlp-proto/tsconfig.json, experimental/packages/opentelemetry-browser-detector/tsconfig.json, experimental/packages/opentelemetry-exporter-metrics-otlp-grpc/tsconfig.json, experimental/packages/opentelemetry-exporter-metrics-otlp-http/tsconfig.json, experimental/packages/opentelemetry-exporter-metrics-otlp-proto/tsconfig.json, experimental/packages/opentelemetry-exporter-prometheus/tsconfig.json, experimental/packages/opentelemetry-instrumentation-fetch/tsconfig.json, experimental/packages/opentelemetry-instrumentation-grpc/tsconfig.json, experimental/packages/opentelemetry-instrumentation-http/tsconfig.json, experimental/packages/opentelemetry-instrumentation-xml-http-request/tsconfig.json, experimental/packages/opentelemetry-instrumentation/tsconfig.json, experimental/packages/opentelemetry-propagator-env-carrier/tsconfig.json, experimental/packages/opentelemetry-sdk-node/tsconfig.json, experimental/packages/otlp-exporter-base/tsconfig.json, experimental/packages/otlp-grpc-exporter-base/tsconfig.json, experimental/packages/otlp-transformer/tsconfig.json, experimental/packages/sampler-composite/tsconfig.json, experimental/packages/sampler-jaeger-remote/tsconfig.json, experimental/packages/web-common/tsconfig.json, packages/opentelemetry-context-async-hooks/tsconfig.json, packages/opentelemetry-context-zone-peer-dep/tsconfig.json, packages/opentelemetry-context-zone/tsconfig.json, packages/opentelemetry-core/tsconfig.json, packages/opentelemetry-exporter-zipkin/tsconfig.json, packages/opentelemetry-propagator-b3/tsconfig.json, packages/opentelemetry-resources/tsconfig.json, packages/sdk-logs/tsconfig.json, packages/sdk-metrics/tsconfig.json, packages/sdk-trace/tsconfig.json, packages/template/tsconfig.json, semantic-conventions/tsconfig.json, tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 18 of the last 100 commits are automated dependency updates
8/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsapi/tsconfig.json, bundler-tests/node/typescript-legacy/tsconfig.json, examples/dice/instrumented/tsconfig.json, examples/dice/uninstrumented/tsconfig.json, examples/esm-http-ts/tsconfig.json, experimental/examples/declarative-config/tsconfig.json, experimental/packages/api-config/tsconfig.json, experimental/packages/configuration/tsconfig.json, experimental/packages/exporter-logs-otlp-grpc/tsconfig.json, experimental/packages/exporter-logs-otlp-http/tsconfig.json, experimental/packages/exporter-logs-otlp-proto/tsconfig.json, experimental/packages/exporter-trace-otlp-grpc/tsconfig.json, experimental/packages/exporter-trace-otlp-http/tsconfig.json, experimental/packages/exporter-trace-otlp-proto/tsconfig.json, experimental/packages/opentelemetry-browser-detector/tsconfig.json, experimental/packages/opentelemetry-exporter-metrics-otlp-grpc/tsconfig.json, experimental/packages/opentelemetry-exporter-metrics-otlp-http/tsconfig.json, experimental/packages/opentelemetry-exporter-metrics-otlp-proto/tsconfig.json, experimental/packages/opentelemetry-exporter-prometheus/tsconfig.json, experimental/packages/opentelemetry-instrumentation-fetch/tsconfig.json, experimental/packages/opentelemetry-instrumentation-grpc/tsconfig.json, experimental/packages/opentelemetry-instrumentation-http/tsconfig.json, experimental/packages/opentelemetry-instrumentation-xml-http-request/tsconfig.json, experimental/packages/opentelemetry-instrumentation/tsconfig.json, experimental/packages/opentelemetry-propagator-env-carrier/tsconfig.json, experimental/packages/opentelemetry-sdk-node/tsconfig.json, experimental/packages/otlp-exporter-base/tsconfig.json, experimental/packages/otlp-grpc-exporter-base/tsconfig.json, experimental/packages/otlp-transformer/tsconfig.json, experimental/packages/sampler-composite/tsconfig.json, experimental/packages/sampler-jaeger-remote/tsconfig.json, experimental/packages/web-common/tsconfig.json, packages/opentelemetry-context-async-hooks/tsconfig.json, packages/opentelemetry-context-zone-peer-dep/tsconfig.json, packages/opentelemetry-context-zone/tsconfig.json, packages/opentelemetry-core/tsconfig.json, packages/opentelemetry-exporter-zipkin/tsconfig.json, packages/opentelemetry-propagator-b3/tsconfig.json, packages/opentelemetry-resources/tsconfig.json, packages/sdk-logs/tsconfig.json, packages/sdk-metrics/tsconfig.json, packages/sdk-trace/tsconfig.json, packages/template/tsconfig.json, semantic-conventions/tsconfig.json, tsconfig.json
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0.18
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.5/55Manageable file sizes — 9/1,083 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes754,018
source_files_sampled1,083
oversized_source_files9
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — experimental/packages/opentelemetry-instrumentation-grpc/test/fixtures/grpc-test.proto, experimental/packages/otlp-transformer/test/fixtures/testbed.proto
0/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesexperimental/packages/opentelemetry-instrumentation-grpc/test/fixtures/grpc-test.proto, experimental/packages/otlp-transformer/test/fixtures/testbed.proto
interfaces_expected_ofnetwork-service

Key facts

0GitHub stars
97contributors
744commits, last 12 months
2days since last push
44releases
5bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Community profile unavailable
  • npm package '@opentelemetry/api' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring
  • npm package '@opentelemetry/semantic-conventions' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring
  • npm package '@opentelemetry/sdk-logs' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring
  • npm package '@opentelemetry/sdk-trace' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring
  • npm package '@opentelemetry/sdk-metrics' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring
  • npm package '@opentelemetry/core' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring
  • npm package '@opentelemetry/resources' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring
  • npm package '@opentelemetry/context-zone' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring
  • npm package '@opentelemetry/propagator-b3' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring
  • npm package '@opentelemetry/exporter-zipkin' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 6.0 / 10
6.0aggregate

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-11-16 19:56 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/30 approved changesets -- score normalized to 0
10Contributorsproject has 41 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
n/aPackagingpackaging workflow not detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
10SASTSAST tool detected: CodeQL
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities32 existing vulnerabilities detected
Direct dependencies 32
RegistryPackageVersion constraintManifest
npm@opentelemetry/api^1.3.0e2e-tests/package.json
npm@opentelemetry/exporter-logs-otlp-proto0.301.2e2e-tests/package.json
npm@opentelemetry/exporter-metrics-otlp-proto0.301.2e2e-tests/package.json
npm@opentelemetry/exporter-trace-otlp-proto0.301.2e2e-tests/package.json
npm@opentelemetry/sdk-logs3.1.1e2e-tests/package.json
npm@opentelemetry/sdk-metrics3.1.1e2e-tests/package.json
npm@opentelemetry/sdk-node0.301.2e2e-tests/package.json
npm@opentelemetry/sdk-trace3.1.1e2e-tests/package.json
npm@opentelemetry/api^1.3.0integration-tests/propagation-validation-server/package.json
npm@opentelemetry/context-async-hooks3.1.1integration-tests/propagation-validation-server/package.json
npm@opentelemetry/core3.1.1integration-tests/propagation-validation-server/package.json
npm@opentelemetry/sdk-trace3.1.1integration-tests/propagation-validation-server/package.json
npmaxios1.20.0integration-tests/propagation-validation-server/package.json
npmbody-parser2.4.0integration-tests/propagation-validation-server/package.json
npmexpress5.1.0integration-tests/propagation-validation-server/package.json
npm@opentelemetry/context-zone-peer-dep3.1.1packages/opentelemetry-context-zone/package.json
npmzone.js^0.11.0 || ^0.12.0 || ^0.13.0 || ^0.14.0 || ^0.15.0 || ^0.16.0packages/opentelemetry-context-zone/package.json
npm@opentelemetry/semantic-conventions^1.29.0packages/opentelemetry-core/package.json
npm@opentelemetry/core3.1.1packages/opentelemetry-exporter-zipkin/package.json
npm@opentelemetry/sdk-trace3.1.1packages/opentelemetry-exporter-zipkin/package.json
npm@opentelemetry/semantic-conventions^1.29.0packages/opentelemetry-exporter-zipkin/package.json
npm@opentelemetry/core3.1.1packages/opentelemetry-propagator-b3/package.json
npm@opentelemetry/core3.1.1packages/opentelemetry-resources/package.json
npm@opentelemetry/semantic-conventions^1.29.0packages/opentelemetry-resources/package.json
npm@opentelemetry/core3.1.1packages/sdk-logs/package.json
npm@opentelemetry/resources3.1.1packages/sdk-logs/package.json
npm@opentelemetry/semantic-conventions^1.29.0packages/sdk-logs/package.json
npm@opentelemetry/core3.1.1packages/sdk-metrics/package.json
npm@opentelemetry/resources3.1.1packages/sdk-metrics/package.json
npm@opentelemetry/core3.1.1packages/sdk-trace/package.json
npm@opentelemetry/resources3.1.1packages/sdk-trace/package.json
npm@opentelemetry/semantic-conventions^1.29.0packages/sdk-trace/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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