@authenio/xml-encryptionnpm
- latest 6.0.2
- last known licence MIT
- stars 41
- assessment attempted 15 days ago
- GitHub evidence observed 15 days ago
- registry checked 15 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 3 years without a release, @authenio/xml-encryption published 6.0.2 on 2026-10-21.
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 3 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=12. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
- Open milestones — v1.1.0 3/3 done; v1.2.0 1/3 done; v2.0.0 0/1 done; v3.0.1 1/1 done. Source: the repository's milestones.
- OpenSSF Scorecard — 6.7 / 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 18 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-22 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@authenio/xml-encryption)Watch it
Get told when @authenio/xml-encryption 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.