registry/internal/validators
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Thomas Thomsen d813d2b805
fix(validators): distinguish a missing package from a missing version on PyPI/NPM (#1411)
Fixes #553.

The PyPI and npm validators fetch the version-specific metadata endpoint
(`/pypi/{name}/{version}/json` and the npm equivalent) and report any
non-200 as `<pkg> not found`. That endpoint 404s for two different
reasons though: the package doesn't exist, or it exists and only the
*version* is missing (e.g. a release that hasn't propagated yet). So a
valid package reads as gone:

```diff
- PyPI package 'requests' not found (status: 404)
+ PyPI package 'requests' exists, but version '99.99.99' was not found (status: 404). A newly published release can take a moment to appear on PyPI. Wait and retry, or publish version '99.99.99' before registering it
```

On a version 404 it probes the package-level endpoint
(`/pypi/{name}/json`, `/{name}`) with a `HEAD` to tell the two apart,
and reports 429/5xx as transient rather than "not found". `HEAD` so it
reads a status without pulling the whole packument. The probe carries
its own 3s deadline: it only refines the error message, so a hung probe
must not stretch the validator past the ~10s-per-registry budget the
publish path assumes. Same probe-and-classify shape as the existing
cargo validator.

The fetch is split into `validatePyPIPackage` / `validateNPMPackage`
behind `export_test.go` so the branches are testable with `httptest`,
the same seam cargo uses.

### Testing
- [x] hermetic `httptest` for the status matrix (version-missing,
package-missing, 5xx, 429, inconclusive probe, positive path, scoped
npm); the mocks pin the expected method per endpoint (`GET` fetch,
`HEAD` probe)
- [x] hermetic deadline test: a hung probe is cut off at ~3s and
reported as inconclusive, not "not found"
- [x] existing live package tests still pass, now also hitting the HEAD
probe; on a live 429/5xx they now `t.Skip` as inconclusive instead of
flaking (deliberate: CI runs these against the real registries with no
short-mode gating)
- [x] `gofmt` / `go vet` / `golangci-lint` clean

Out of scope: auto-retry for the propagation race, and SSRF
redirect-pinning parity for the pypi/npm clients (pre-existing, shared
with nuget).
2026-07-12 15:24:34 -04:00
..
registries fix(validators): distinguish a missing package from a missing version on PyPI/NPM (#1411) 2026-07-12 15:24:34 -04:00
schemas security: fix open redirect and add small hardening (#1227) 2026-04-29 19:14:00 -04:00
constants.go feat: Add LocalTransport/RemoteTransport with URL template variables (#570) 2025-12-11 09:17:32 -08:00
package.go feat: add cargo (crates.io) as a package registry type (#1207) 2026-06-03 10:56:43 -04:00
schema.go Stop pinning Go to patch versions, use stable in CI (#1137) 2026-04-09 11:57:21 -04:00
schema_regex_test.go update schema url point to the actual location (#884) 2026-02-10 13:32:58 -08:00
schema_test.go Enhanced server.json validation (phase 1) (#636) 2026-01-16 00:49:39 +02:00
utils.go feat: Add LocalTransport/RemoteTransport with URL template variables (#570) 2025-12-11 09:17:32 -08:00
validation_detailed_test.go Enhanced server.json validation (phase 1) (#636) 2026-01-16 00:49:39 +02:00
validation_types.go Enhanced server.json validation (phase 1) (#636) 2026-01-16 00:49:39 +02:00
validation_types_test.go Enhanced server.json validation (phase 1) (#636) 2026-01-16 00:49:39 +02:00
validators.go fix(validators): reject HTML metacharacters and whitespace in websiteUrl (#1249) 2026-05-04 09:26:50 -04:00
validators_test.go fix(validators): reject HTML metacharacters and whitespace in websiteUrl (#1249) 2026-05-04 09:26:50 -04:00