loopback-component-explorernpm
- latest 6.5.1
- licence MIT
- stars 69
- assessment attempted 4 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
0
Open issues
1
Unanswered
0
Contributors
0
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=8.9. Source: the registry.
- Publishers on the registry — 4. Source: the registry.
- Open milestones — April 2018 (due 2018-04-30); August milestone (due 2018-08-02); August Milestone (due 2018-08-31); November 2018 Milestone (due 2018-11-30); December 2018 Milestone (due 2018-12-31). Source: the repository's milestones.
- OpenSSF Scorecard — 3.5 / 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 4 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-15 | first verdict: finished |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/loopback-component-explorer)Watch it
Get told when loopback-component-explorer 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.