@salesforce/prettier-confignpm
- latest 0.0.5
- last known licence Apache-2.0
- stars 3
- 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, @salesforce/prettier-config published 0.0.5 on 2026-10-15.
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, 0.0.5, carries a signed provenance attestation. Source: the registry.
- Publishers on the registry — 7. Source: the registry.
- Security policy — published. Source: the repository.
Third-party facts checked 26 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-17 | first verdict: active |
Licence history 1
| When | Change | Severity |
|---|---|---|
| 2026-09-03 | BSD-3-Clause → Apache-2.0 (0.0.4) | info |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@salesforce/prettier-config)Watch it
Get told when @salesforce/prettier-config 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.