@prettier/plugin-pugnpm
- latest 3.6.0
- last known licence MIT
- stars 207
- assessment attempted 26 days ago
- GitHub evidence observed 26 days ago
- registry checked 26 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 →Came back
After 14 months without a release, @prettier/plugin-pug published 3.6.0 on 2026-10-05.
Usually this is a maintainer returning. It is also what a hijacked package looks like, so it is worth a glance at what changed before you upgrade.
Maintenance trends
Loading historical repository activity…
Signals · last 10 checks
What the project says about itself
- Build provenance — the latest release, 3.6.0, carries a signed provenance attestation. Source: the registry.
- Supported runtime — node >=22.0.0. Source: the registry.
- Publishers on the registry — 14. Source: the registry.
- Funding — github.com/Shinigami92, www.paypal.com/donate/?hosted_button_id=L7GY729FBKTZY. Source: the registry.
- OpenSSF Scorecard — 5.2 / 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 26 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-17 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@prettier/plugin-pug)Watch it
Get told when @prettier/plugin-pug 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.