CodeSampleX

Recordsgolanggo.opentelemetry.io/otelv1.44.0

Change the conditions
Fixed
Package versionv1.44.0 Package managergo
Filter OSalpine musl Runtimego 1.26 Symbolwhole package Architecturex64 Execution contextgo libcmusl Clear filters

Current conditions

go.opentelemetry.io/otel @v1.44.0alpine musl · x64 · go 1.26 · go · go

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (8)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-08

Dependency Health

Observed combinations and failure evidence for this release

Changed 6 · Steady 2

Dependency changes observed: 6. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
github.com/go-logr/logr v1.4.3 CHANGED Version changed, no linked failure contract passed 22 project-days
github.com/google/go-cmp v0.7.0 CHANGED Version changed, no linked failure contract passed 22 project-days
github.com/stretchr/testify v1.11.1 CHANGED Version changed, no linked failure contract passed 19 project-days
go.opentelemetry.io/auto/sdk v1.2.1 CHANGED Version changed, no linked failure contract passed 22 project-days
go.opentelemetry.io/otel/metric v1.44.0 CHANGED Version changed, no linked failure builds observed 22 project-days
go.opentelemetry.io/otel/trace v1.44.0 CHANGED Version changed, no linked failure builds observed 22 project-days
github.com/cespare/xxhash/v2 v2.3.0 PASS All observations passed contract passed 22 project-days
github.com/go-logr/stdr v1.2.2 PASS All observations passed contract passed 22 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Moved: 6 · unchanged at every release: 2

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.