Recordsgolanggolang.org/x/textv0.5.0
Change the conditions
Current conditions
golang.org/x/text @v0.5.0debian glibc · 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.
no sample at this coordinate yet
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-01
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| golang.org/x/mod | v0.6.0-dev.0.20220419223038-86c51ed26bb4 | contract passed | 1 project-day |
| golang.org/x/sys | v0.47.0 | contract passed | 1 project-day |
| golang.org/x/tools | v0.1.12 | contract passed | 1 project-day |
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.
| Library | v0.37.0 | v0.36.0 | v0.35.0 | v0.5.0 |
|---|---|---|---|---|
| golang.org/x/tools | v0.44.0 | v0.44.0 | v0.42.0 | v0.1.12 |
| golang.org/x/mod | — | — | — | v0.6.0-dev.0.20220419223038-86c51ed26bb4 |
| golang.org/x/sys | — | — | — | v0.47.0 |
Moved: 1 · 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.