You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
馃摙 This repository is being archived (read-only) on 2 November 2026聽#50
We are letting the community know that node-wsfed will be archived on 2 November 2026 and will become read-only.
This library implements the server (IdP) side of the WS-Federation protocol in Node.js. It has not received active feature development for some time, and we have decided to formally archive it rather than continue presenting it as actively maintained.
What this means
The repository will be archived (read-only) on 2 November 2026. After that date, Issues and Pull Requests will be disabled.
We are not looking to transfer ownership of this project to a new maintainer.
All existing releases remain available, and the wsfed npm package will remain installable, we are not unpublishing anything.
The wsfed npm package will be marked as deprecated on 4 January 2027 (after a grace period to avoid breaking existing tooling). It will remain installable.
What you should do
We encourage all users and dependents to find a replacement that fits their needs.
Please note there is no direct, drop-in Auth0-maintained replacement. Evaluate community alternatives carefully against your security and maintenance requirements.
npm package
To avoid breaking existing tooling and CI pipelines, the wsfed npm package will not be marked as deprecated immediately. We plan to mark it as deprecated on 4 January 2027, after a grace period. The package will remain installable.
Timeline
Date
What happens
12 August 2026
This announcement; README updated.
2 November 2026
Repository archived; Issues and PRs disabled.
4 January 2027
wsfed npm package marked as deprecated.
Thank you to everyone who has used and contributed to this project over the years.
Activity
docs: add archival notice to README (#51)