@uppy/xhr-uploadnpm
- latest 6.0.1
- last known licence MIT
- stars 31,066
- assessment attempted 2 days ago
- GitHub evidence observed 2 days ago
- registry checked 6 days ago
- registry ↗
- repository ↗
Vulnerabilities, end of life and next steps
Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Maintenance trends
Loading historical repository activity…
Signals · last 3 checks
Commits 90d
100
Open issues
157
Unanswered
48
Contributors
12
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 4. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Minimum Valuable Product 22/22 done; Nice to haves after MVP. Source: the repository's milestones.
- OpenSSF Scorecard — 6.4 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked 6 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-13 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@uppy/xhr-upload)Watch it
Get told when @uppy/xhr-upload changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.