@itwin/express-servernpm
- latest 5.14.3
- last known licence MIT
- stars 736
- assessment attempted 22 days ago
- GitHub evidence observed 22 days ago
- registry checked 22 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 2 checks
Commits 90d
100
Open issues
367
Unanswered
191
Contributors
16
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node ^20.0.0 || ^22.0.0 || ^24.0.0. Source: the registry.
- Publishers on the registry — 5. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — iTwin.js 6.0 0/6 done; iTwin.js 5.15 (due 2026-11-01) 3/11 done; iTwin.js 5.16 (due 2026-12-01). Source: the repository's milestones.
Third-party facts checked 22 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-19 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@itwin/express-server)Watch it
Get told when @itwin/express-server 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.