@middy/response-loggernpm
- latest 0.0.0-alpha.0
- last known licence MIT
- stars 3,904
- assessment attempted 10 days ago
- GitHub evidence observed 10 days ago
- registry checked 10 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
3
Unanswered
0
Contributors
3
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=24. Source: the registry.
- Publishers on the registry — 3. Source: the registry.
- Funding — github.com/sponsors/willfarrell. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — v6 8/8 done; v7 1/2 done; v8 1/3 done; v4 (due 2023-04-30) 7/7 done; v5 (due 2023-11-01) 8/8 done. Source: the repository's milestones.
- OpenSSF Scorecard — 9.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 on 2026-09-28; registry facts on every crawl.
State history 2
| When | Change |
|---|---|
| 2026-10-27 | active → abandoned |
| 2026-09-28 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@middy/response-logger)Watch it
Get told when @middy/response-logger 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.