Dependency health Workspace

@vuept/loopback-connector-mssqlnpm

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 →
What the project says about itself
  • Build provenance — the latest release carries no provenance attestation. Source: the registry.
  • Supported runtimenode >=10. Source: the registry.
  • Publishers on the registry — 1. Source: the registry.
  • Security policypublished. Source: the repository.
  • Open milestonesApril 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 Scorecard4.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 yesterday; registry facts on every crawl.

State history 1
WhenChange
2026-09-17 first verdict: finished

Badge

maintenance: finished

Drop this in your README. It re-renders itself as the verdict changes.

[![maintenance](https://isitdeadyet.dev/badge/npm/@vuept/loopback-connector-mssql.svg)](https://isitdeadyet.dev/npm/@vuept/loopback-connector-mssql)

Watch it

Get told when @vuept/loopback-connector-mssql 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.