Records/golang/github.com/Masterminds/semver/v3/v3.2.0/semver.Collection

Published samples

• github.com/Masterminds/semver/v3 v3.2.0: semver.Collection, semver.NewConstraint, semver.NewVersion Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWsemver.Collectionsemver.NewConstraintsemver.NewVersionsemver.StrictNewVersionsemver.Version.IncMajorsemver.Version.IncMinorsemver.Version.IncPatchgo 1.26.6 MIT-0 · 2026-08-28

Compatibility matrix

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

snapshot · 2026-09-15

Failure clusters

• observed UNKNOWN exit 1 Evidence gap ×1 v3.2.0 os=linux · runtime=go@1.26 sha256:876aedbfdb15…
  FAIL: expected 2.0.2 with cleared prerelease and metadata, got 2.0.1 (pre: , meta: ) · exit status 1
  go · unclassified-diagnostic · outer go run · gap stage-unknown
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
  Diagnostic re-verification candidate
  Where does this failure start and stop?