CodeSampleX

Recordsgolanggithub.com/google/pprofv0.0.0-20260906184651-6331bc6350fegithub.com/google/pprof/profile.Function

Change the conditions
Fixed
OSdebian glibc Package versionv0.0.0-20260906184651-6331bc6350fe Symbolgithub.com/google/pprof/profile.Function
Filter Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

github.com/google/pprof/profile.Function @v0.0.0-20260906184651-6331bc6350fedebian glibc · x64 · go 1.26 · go · go

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
2 / 2
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-10-10

Dependency Health

Observed combinations and failure evidence for this release

Changed 2 · Steady 0

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

Library Version Health Measured there Projects
github.com/chzyer/readline v1.5.1 CHANGED Version changed, no linked failure contract passed 8 project-days
github.com/ianlancetaylor/demangle v0.0.0-20250417193237-f615e6bd150b CHANGED Version changed, no linked failure builds observed 8 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: 2 · unchanged at every release: 1

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.