@discordjs/utilnpm
- latest 1.2.0
- last known licence Apache-2.0
- stars 26,827
- assessment attempted yesterday
- GitHub evidence observed yesterday
- registry checked 19 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 16 checks
Commits 90d
43
Open issues
97
Unanswered
29
Contributors
37
What the project says about itself
- Build provenance — the latest release, 1.2.0, carries a signed provenance attestation. Source: the registry.
- Supported runtime — node >=18. Source: the registry.
- Publishers on the registry — 2. Source: the registry.
- Funding — github.com/discordjs/discord.js?sponsor. Source: the registry.
- Open milestones — TypeScript Rewrite 0/6 done; builders 2.0.0 46/49 done; next 0.1.0; rest 3.0.0 12/13 done; proxy 3.0. Source: the repository's milestones.
- OpenSSF Scorecard — 5.7 / 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 17 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-07 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@discordjs/util)Watch it
Get told when @discordjs/util 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.