Need help with project support?

[glukki]

Seem like this project need some love and maintenance help.

No updates since December 2016, master branch is broken (yes, with simple typo, but still!).
I use this module in my client's project, so I'm interested in this module staying alive :)

@bergie @pdspicer do you need help? I could become a maintainer

[vvo]

Seems like https://github.com/auth0/passport-wsfed-saml2 might be a good alternative, anyone tried it?

[vvo]

Also https://github.com/tngan/samlify

[markstos]

@glukki Considering that there's been response in several months, consider a fork-and-release.

[bergie]

If somebody wants to help maintain, I can give NPM publish rights

[markstos]

I can help push the 0.16 release out, but can't promise much bandwidth on an ongoing basis. I'm also a co-maintainer of the popular node-config module, which has a fairly steady support stream in the issue tracker. My username on NPM is markstos, same as on Github.

[bergie]

@markstos done!

[markstos]

@bergie I can confirm that I have NPM publish rights. Could I also have Github commit rights? At the moment I want to push a Github tag so that the release is reflected on Github as well. Thanks.

[josecolella]

@bergie @markstos Is there a need for help for the project?

[markstos]

@josecolella Yes. @bergie is no longer active with the project. I've been helping as the maintainer, but am spread thin with other job responsibilities.

[josecolella]

@markstos I can help with maintaining the project. I think passport-saml is a great library that provides simplicity and ease of use with passport and is easily integrated in projects that use express.

[markstos]

@josecolella Thanks. You are welcome to put together the next potential release in a branch of your own. I'll pledge to do a timely peer-review-merge-and-release once that's done. My bar for quality includes:

• For any spec-related change, reference the specific place in the SAML spec that discusses the topic.
• Update documentation where appropriate and update automated tests when feasible.

I'm mindful that an exploit in passport-saml could have a big impact, so I pay close attention to any changes that appear that they could have security implications.

If the collaboration goes well, perhaps @bergie could provide direct commit access (I can't).

[markstos]

Last time I looked at NPM stats, this module was still the #1 SAML solution for Node.js.

Some people are already using it without also using Passport, and I think it would benefit from completing the de-coupling and putting the core SAML functionality in it's own library, released separately.

I think that could attract more users and hopefully then more contributors. It could also help with security: "with enough eyeballs, all bugs are shallow".