Recordsgolangmodernc.org/gc/v3v3.1.5
Change the conditions
Current conditions
modernc.org/gc/v3 @v3.1.5debian 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-07
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/tools | v0.48.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| github.com/dustin/go-humanize | v1.0.1 | PASS All observations passed | contract passed | 1 project-day |
| github.com/hashicorp/golang-lru/v2 | v2.0.7 | PASS All observations passed | contract passed | 1 project-day |
| modernc.org/mathutil | v1.7.1 | PASS All observations passed | contract passed | 1 project-day |
| modernc.org/strutil | v1.2.1 | PASS All observations passed | contract passed | 1 project-day |
| modernc.org/token | v1.1.0 | PASS All observations passed | 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.
Moved: 1 · unchanged at every release: 8
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.