Closed binarykitchen closed 9 years ago
@binarykitchen I wouldn't consider that repository, because it only has 4 commits and the last one was 3 months ago with no stars. However, @jaredhanson, this repository has been neglected for some time, and it's a little worrying considering how far back some of these issues go.
The question seems legit though. The number of good PR to merge is worrying. And I can see that there is a fair amount of forks that looks quite advanced.
@jaredhanson, I am sorry to have to ask that but would you consider passing by the ownership to someone else of choose an official fork to use instead?
FYI, anyone who would like to take this on, I would suggest that you just fork it, @jaredhanson is way too slow...and he doesn't seem to want to let anyone help him out...
It would still be nice to know if there is any existing fork that might be well maintained.
Do you currently use any?
Nope, looking around for one. I would start a fork, but I have too much on my plate right now.
You may want to also consider: https://github.com/google/google-api-nodejs-client
Unfortunately it as nothing to do with Passportjs :(
Yes, but I think it's the next best thing given the current scenario. :{}
Only really for google though..
Might also consider using https://github.com/sqrrrl/passport-google-plus
@sqrrrl does that support the state parameter?
@ilanbiala No, but been meaning to add it along with pure server-side flows. Right now it is written to be used with the G+ sign-in button to initiate the auth requests.
All outstanding and relevant pull requests on this package have been merged and a new, up-to-date version is on npm.
Or should I consider https://github.com/shobhitsinghal624/passport-google-authcode ?