Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-26 16:37 UTC

mwear / opentelemetry-js

OpenTelemetry API for Javascript (both Node and browser)

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

mwear/opentelemetry-js holds a health index of 33 out of 100, placing it in the At Risk band. It scores highest on Engineering Quality (69/100) and lowest on Community & Adoption (12/100). It was last updated 17 days ago. 3 contributors account for most of its recent work.

33
overall / 100
At Risk

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.

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

Ownership

Matthew WearPersonal account
44 followers39 public repossince Oct 2012@dash0hq

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
npmopentelemetry-basepoints to another repo — not scored0.9.04592228 days agoopentelemetrynodejsprofilingmetricsstats
npm@opentelemetry/apipoints to another repo — not scored1.9.1265,518,77664123 days agoopentelemetrynodejsbrowsertracingprofilingstatsmonitoring
npm@opentelemetry/corepoints to another repo — not scored2.10.0493,200,5101954 days agoopentelemetrynodejsbrowsertracingprofilingmetricsstats
npm@opentelemetry/plugins-web-core⚠ Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.points to another repo — not scored0.18.276701944 days ago—
npm@opentelemetry/plugins-node-core⚠ Deprecated in favor of @opentelemetry/auto-instrumentations-node and @opentelemetry/auto-instrumentations-webpoints to another repo — not scored0.18.2217691944 days ago—
npm@opentelemetry/api-metrics⚠ Please use @opentelemetry/api >= 1.3.0points to another repo — not scored0.33.03,985,944691409 days agoopentelemetrynodejsbrowserprofilingmetricsstatsmonitoring
npm@opentelemetry/context-base⚠ Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.points to another repo — not scored0.17.0438,299271984 days agoopentelemetrynodejsbrowsertracingprofilingmetricsstats

Metrics by category

Vitality

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

37Weak · 21% of overall

Development activity

29At Risk
How it's scored
28.8/36Push recency — last push 17 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push17
active_weeks_last_year0

Release discipline

48Weak
How it's scored
16.2/27Ships releases — 8 version tags (no GitHub releases)
0/36Release recency — latest release 2,362 days ago
27/27Release cadence — a release every ~16.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count8
latest_release_tagv0.4.0
releases_from_tagsyes
days_since_latest_release2,362
mean_days_between_releases16.7
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

Popularity & adoption

1Critical
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

Community health

25At Risk
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_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

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

46Weak · 23% of overall

Maintainer resilience (bus factor)

75Good
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
15.7/22.5Commit distribution — top contributor authored 30% of commits
13.5/13.5Contributor breadth — 90 contributors
10/10OpenSSF Scorecard: Contributors — project has 29 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled90
top_contributor_share0.302

Issue & PR responsiveness

1Critical
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_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.

Ownership & stewardship

57Moderate
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
11.9/25Owner reach — 44 followers of mwear
23.7/25Track record — 39 public repos, account ~13 yr old
Inputs used
followers44
owner_typeUser
is_verified—
owner_loginmwear
public_repos39
account_age_days5,038
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

Engineering practices

88Excellent
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc, .eslintrc.js, eslint.config.js
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.

Documentation

40Weak
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?

45Weak · 16% of overall

Security posture

45Weak
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 29 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
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
5/5SAST — SAST tool detected: CodeQL
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
5.2/7.5Vulnerabilities — 3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.5
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.

61Moderate · 4% of overall

Agent context & guidance

40Weak
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 100 of 100 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—

Verify loop (build / test / typecheck)

54Moderate
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc, .eslintrc.js, eslint.config.js
11/11Static type checking — backwards-compatability/node10/tsconfig.json, backwards-compatability/node12/tsconfig.json, backwards-compatability/node8/tsconfig.json, integration-tests/propagation-validation-server/tsconfig.json, packages/opentelemetry-api-metrics/tsconfig.json, packages/opentelemetry-api/tsconfig.json, packages/opentelemetry-context-async-hooks/tsconfig.json, packages/opentelemetry-context-base/tsconfig.json, packages/opentelemetry-context-zone-peer-dep/tsconfig.json, packages/opentelemetry-context-zone/tsconfig.json, packages/opentelemetry-core/tsconfig.json, packages/opentelemetry-exporter-collector-grpc/tsconfig.json, packages/opentelemetry-exporter-collector-proto/tsconfig.json, packages/opentelemetry-exporter-collector/tsconfig.json, packages/opentelemetry-exporter-jaeger/tsconfig.json, packages/opentelemetry-exporter-prometheus/tsconfig.json, packages/opentelemetry-exporter-zipkin/tsconfig.json, packages/opentelemetry-grpc-utils/tsconfig.json, packages/opentelemetry-instrumentation-fetch/tsconfig.json, packages/opentelemetry-instrumentation-grpc/tsconfig.json, packages/opentelemetry-instrumentation-http/tsconfig.json, packages/opentelemetry-instrumentation-xml-http-request/tsconfig.json, packages/opentelemetry-instrumentation/tsconfig.json, packages/opentelemetry-metrics/tsconfig.json, packages/opentelemetry-node/tsconfig.json, packages/opentelemetry-plugin-grpc-js/tsconfig.json, packages/opentelemetry-plugin-grpc/tsconfig.json, packages/opentelemetry-plugin-http/tsconfig.json, packages/opentelemetry-plugin-https/tsconfig.json, packages/opentelemetry-propagator-b3/tsconfig.json, packages/opentelemetry-resource-detector-aws/tsconfig.json, packages/opentelemetry-resource-detector-gcp/tsconfig.json, packages/opentelemetry-resources/tsconfig.json, packages/opentelemetry-sdk-node/tsconfig.json, packages/opentelemetry-semantic-conventions/tsconfig.json, packages/opentelemetry-shim-opentracing/tsconfig.json, packages/opentelemetry-tracing/tsconfig.json, packages/opentelemetry-web/tsconfig.json, packages/template/tsconfig.json, tsconfig.json
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsbackwards-compatability/node10/tsconfig.json, backwards-compatability/node12/tsconfig.json, backwards-compatability/node8/tsconfig.json, integration-tests/propagation-validation-server/tsconfig.json, packages/opentelemetry-api-metrics/tsconfig.json, packages/opentelemetry-api/tsconfig.json, packages/opentelemetry-context-async-hooks/tsconfig.json, packages/opentelemetry-context-base/tsconfig.json, packages/opentelemetry-context-zone-peer-dep/tsconfig.json, packages/opentelemetry-context-zone/tsconfig.json, packages/opentelemetry-core/tsconfig.json, packages/opentelemetry-exporter-collector-grpc/tsconfig.json, packages/opentelemetry-exporter-collector-proto/tsconfig.json, packages/opentelemetry-exporter-collector/tsconfig.json, packages/opentelemetry-exporter-jaeger/tsconfig.json, packages/opentelemetry-exporter-prometheus/tsconfig.json, packages/opentelemetry-exporter-zipkin/tsconfig.json, packages/opentelemetry-grpc-utils/tsconfig.json, packages/opentelemetry-instrumentation-fetch/tsconfig.json, packages/opentelemetry-instrumentation-grpc/tsconfig.json, packages/opentelemetry-instrumentation-http/tsconfig.json, packages/opentelemetry-instrumentation-xml-http-request/tsconfig.json, packages/opentelemetry-instrumentation/tsconfig.json, packages/opentelemetry-metrics/tsconfig.json, packages/opentelemetry-node/tsconfig.json, packages/opentelemetry-plugin-grpc-js/tsconfig.json, packages/opentelemetry-plugin-grpc/tsconfig.json, packages/opentelemetry-plugin-http/tsconfig.json, packages/opentelemetry-plugin-https/tsconfig.json, packages/opentelemetry-propagator-b3/tsconfig.json, packages/opentelemetry-resource-detector-aws/tsconfig.json, packages/opentelemetry-resource-detector-gcp/tsconfig.json, packages/opentelemetry-resources/tsconfig.json, packages/opentelemetry-sdk-node/tsconfig.json, packages/opentelemetry-semantic-conventions/tsconfig.json, packages/opentelemetry-shim-opentracing/tsconfig.json, packages/opentelemetry-tracing/tsconfig.json, packages/opentelemetry-web/tsconfig.json, packages/template/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/624 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes47,681
source_files_sampled624
oversized_source_files0

Machine-readable interfaces

80Excellent
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — packages/opentelemetry-grpc-utils/test/fixtures/grpc-test.proto, packages/opentelemetry-instrumentation-grpc/test/fixtures/grpc-test.proto
0/20MCP server
40/40Runnable examples — example, examples
Inputs used
example_dirsexample, examples
has_mcp_signalno
api_schema_filespackages/opentelemetry-grpc-utils/test/fixtures/grpc-test.proto, packages/opentelemetry-instrumentation-grpc/test/fixtures/grpc-test.proto
interfaces_expected_ofnetwork-service

Key facts

0GitHub stars
90contributors
0commits, last 12 months
17days since last push
8releases
3bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Community profile unavailable
  • npm package 'opentelemetry-base' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring
  • npm package '@opentelemetry/api' 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/plugins-web-core' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring
  • Could not fetch npm package '@opentelemetry/getting-started-traced-example' from its registry
  • npm package '@opentelemetry/plugins-node-core' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring
  • Could not fetch npm package '@opentelemetry/getting-started-monitored-example' from its registry
  • npm package '@opentelemetry/api-metrics' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring
  • npm package '@opentelemetry/context-base' points at a different repository (https://github.com/open-telemetry/opentelemetry-js); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 4.5 / 10
4.5aggregate

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-26 16:37 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 29 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool detected: CodeQL
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 70
RegistryPackageVersion constraintManifest
npm@opentelemetry/sdk-node^0.15.0backwards-compatability/node10/package.json
npm@opentelemetry/tracing^0.15.0backwards-compatability/node10/package.json
npm@opentelemetry/sdk-node^0.15.0backwards-compatability/node12/package.json
npm@opentelemetry/tracing^0.15.0backwards-compatability/node12/package.json
npm@opentelemetry/sdk-node^0.15.0backwards-compatability/node8/package.json
npm@opentelemetry/tracing^0.15.0backwards-compatability/node8/package.json
npm@opentelemetry/exporter-prometheus^0.15.0getting-started/monitored-example/package.json
npm@opentelemetry/metrics^0.15.0getting-started/monitored-example/package.json
npmaxios^0.21.0getting-started/monitored-example/package.json
npmexpress^4.17.1getting-started/monitored-example/package.json
npm@opentelemetry/core^0.15.0getting-started/traced-example/package.json
npm@opentelemetry/exporter-zipkin^0.15.0getting-started/traced-example/package.json
npm@opentelemetry/node^0.15.0getting-started/traced-example/package.json
npm@opentelemetry/plugin-express^0.12.0getting-started/traced-example/package.json
npm@opentelemetry/plugin-http^0.15.0getting-started/traced-example/package.json
npm@opentelemetry/plugin-https^0.15.0getting-started/traced-example/package.json
npm@opentelemetry/tracing^0.15.0getting-started/traced-example/package.json
npmaxios^0.21.0getting-started/traced-example/package.json
npmexpress^4.17.1getting-started/traced-example/package.json
npm@opentelemetry/api^0.15.0integration-tests/propagation-validation-server/package.json
npm@opentelemetry/context-async-hooks^0.15.0integration-tests/propagation-validation-server/package.json
npm@opentelemetry/core^0.15.0integration-tests/propagation-validation-server/package.json
npm@opentelemetry/tracing^0.15.0integration-tests/propagation-validation-server/package.json
npmaxios0.21.1integration-tests/propagation-validation-server/package.json
npmbody-parser1.19.0integration-tests/propagation-validation-server/package.json
npmexpress4.17.1integration-tests/propagation-validation-server/package.json
npm@opentelemetry/plugin-grpc^0.15.0metapackages/plugins-node-core/package.json
npm@opentelemetry/plugin-grpc-js^0.15.0metapackages/plugins-node-core/package.json
npm@opentelemetry/plugin-http^0.15.0metapackages/plugins-node-core/package.json
npm@opentelemetry/plugin-https^0.15.0metapackages/plugins-node-core/package.json
npm@opentelemetry/instrumentation-xml-http-request^0.15.0metapackages/plugins-web-core/package.json
npm@opentelemetry/api^0.15.0packages/opentelemetry-api-metrics/package.json
npm@opentelemetry/context-base^0.15.0packages/opentelemetry-api/package.json
npm@opentelemetry/context-base^0.15.0packages/opentelemetry-context-async-hooks/package.json
npm@opentelemetry/context-base^0.15.0packages/opentelemetry-context-zone-peer-dep/package.json
npm@opentelemetry/context-zone-peer-dep^0.15.0packages/opentelemetry-context-zone/package.json
npmzone.js^0.11.0packages/opentelemetry-context-zone/package.json
npm@opentelemetry/api^0.15.0packages/opentelemetry-core/package.json
npm@opentelemetry/context-base^0.15.0packages/opentelemetry-core/package.json
npmsemver^7.1.3packages/opentelemetry-core/package.json
npm@grpc/proto-loader^0.5.4packages/opentelemetry-exporter-collector-grpc/package.json
npm@opentelemetry/api^0.15.0packages/opentelemetry-exporter-collector-grpc/package.json
npm@opentelemetry/core^0.15.0packages/opentelemetry-exporter-collector-grpc/package.json
npm@opentelemetry/exporter-collector^0.15.0packages/opentelemetry-exporter-collector-grpc/package.json
npm@opentelemetry/metrics^0.15.0packages/opentelemetry-exporter-collector-grpc/package.json
npm@opentelemetry/resources^0.15.0packages/opentelemetry-exporter-collector-grpc/package.json
npm@opentelemetry/tracing^0.15.0packages/opentelemetry-exporter-collector-grpc/package.json
npmgrpc^1.24.2packages/opentelemetry-exporter-collector-grpc/package.json
npm@grpc/proto-loader^0.5.4packages/opentelemetry-exporter-collector-proto/package.json
npm@opentelemetry/api^0.15.0packages/opentelemetry-exporter-collector-proto/package.json
npm@opentelemetry/core^0.15.0packages/opentelemetry-exporter-collector-proto/package.json
npm@opentelemetry/exporter-collector^0.15.0packages/opentelemetry-exporter-collector-proto/package.json
npm@opentelemetry/metrics^0.15.0packages/opentelemetry-exporter-collector-proto/package.json
npm@opentelemetry/resources^0.15.0packages/opentelemetry-exporter-collector-proto/package.json
npm@opentelemetry/tracing^0.15.0packages/opentelemetry-exporter-collector-proto/package.json
npmprotobufjs^6.9.0packages/opentelemetry-exporter-collector-proto/package.json
npm@opentelemetry/api^0.15.0packages/opentelemetry-exporter-collector/package.json
npm@opentelemetry/api-metrics^0.15.0packages/opentelemetry-exporter-collector/package.json
npm@opentelemetry/core^0.15.0packages/opentelemetry-exporter-collector/package.json
npm@opentelemetry/metrics^0.15.0packages/opentelemetry-exporter-collector/package.json
npm@opentelemetry/resources^0.15.0packages/opentelemetry-exporter-collector/package.json
npm@opentelemetry/tracing^0.15.0packages/opentelemetry-exporter-collector/package.json
npm@opentelemetry/api^0.15.0packages/opentelemetry-exporter-jaeger/package.json
npm@opentelemetry/core^0.15.0packages/opentelemetry-exporter-jaeger/package.json
npm@opentelemetry/tracing^0.15.0packages/opentelemetry-exporter-jaeger/package.json
npmjaeger-client^3.15.0packages/opentelemetry-exporter-jaeger/package.json
npm@opentelemetry/api^0.15.0packages/opentelemetry-exporter-prometheus/package.json
npm@opentelemetry/api-metrics^0.15.0packages/opentelemetry-exporter-prometheus/package.json
npm@opentelemetry/core^0.15.0packages/opentelemetry-exporter-prometheus/package.json
npm@opentelemetry/metrics^0.15.0packages/opentelemetry-exporter-prometheus/package.json
All dependencies 0

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

RegistryPackageVersionRelation
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies to assess

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with mwear/opentelemetry-js. Read them side by side →

100clerk/javascriptOfficial JavaScript repository for Clerk authenticationExceptional100withastro/astroThe web framework for content-driven websites. ⭐️ Star to support our work!Exceptional100dotnet/aspnetcoreASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.Exceptional100mui/material-uiMaterial UI: Comprehensive React component library that implements Google's Material Design. Free forever.Exceptional100coder/coderSecure environments for developers and their agentsExceptional100ionic-team/ionic-frameworkA powerful cross-platform UI toolkit for building native-quality iOS, Android, and Progressive Web Apps with HTML, CSS, and JavaScript.Exceptional

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.27.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.