@rayspec/bundle-closurenpm
- latest 1.9.1
- licence FSL-1.1-ALv2
- stars 0
- assessment attempted 8 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 1 check
The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.
Commits 90d
100
Open issues
18
Unanswered
6
Contributors
1
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=22.21.0. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
- Security policy — published. Source: the repository.
Third-party facts checked 8 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-11 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@rayspec/bundle-closure)Watch it
Get told when @rayspec/bundle-closure 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.