Recordsgolanggo.opentelemetry.io/otel/exporters/stdout/stdouttrace
Change the conditions
Current conditions
go.opentelemetry.io/otel/exporters/stdout/stdouttrace @v1.43.0alpine musl · x64 · go 1.26 · go · go
2 of 4 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and this coordinate records both a passing and a failing run of it (2)
- Project observations
- 2 / 2
- Contract verifications
- 2 / 4
- Usage records
- 2
- Independent reporting peers
- 1
- Cross-checked
- reproduced by two or more independent peers
- Last recorded
- 2026-08-31
Evidence you can open
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
2 of 4 passed
Verified — this network ran a contract at this coordinate.
-
stdouttrace.Exporter
2 of 4 passed
Verified — this network ran a contract at this coordinate.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| github.com/stretchr/testify | v1.11.1 | contract passed | 2 project-days |
| go.opentelemetry.io/otel | v1.43.0 | contract passed | 2 project-days |
| go.opentelemetry.io/otel/metric | v1.43.0 | contract passed | 2 project-days |
| go.opentelemetry.io/otel/sdk | v1.43.0 | contract passed | 2 project-days |
| go.opentelemetry.io/otel/sdk/metric | v1.43.0 | contract passed | 2 project-days |
| go.opentelemetry.io/otel/trace | v1.43.0 | contract passed | 2 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.