npm
[WIP] rfc: allow token exclusion for write 2fa
i still have work to do to shape this proposal out completely, but thought there is enough here to open up for early feedback.
for reference, this is a continuation of the conversation started here
Thank you for writing up such a detailed discussion of your needs.
This is a use-case that we've discussed regarding 2fa internally at npm, and its one that we intend to support. We've not sat down and drawn up exactly what our plans are yet, but something roughly like what's described here is one of the ideas raised previously.
I'm going to leave this open until we do that work and finalize our plans, at which point we'll update this with those plans.
great to hear. i apologize for not getting back to this before now to flesh it out a bit further, but it sounds like i should hold off for now.
my team is pretty aggressive with automating things and following continuous deployment of our packages, so i'd be more than happy to help out the conversation any way i can, especially if our flow helps with walking through concrete examples.
looking forward to see where this ends up. thank you for all your efforts and for the interest in input from the community.
It might be going one step too far for this RFC, but I think limiting the non-MFA token to do one specific thing (publish just one package) would make this more secure.
In my case I would like to automate the publication of a package that is used internally, but would not want to put more popular packages where I have publication rights at risk if the token was exposed. Allowing the creation of a special non-MFA single use publication token would solve this issue, and I think help with several of the contingencies raised by @travi's write up.
Also - It's a promise with no weight, but I would easily be able to justify my organization paying for the private package upgrade if it included this feature. 😄
