[hypeatei]

> Anything I'm overlooking here?

Not technical, but the person behind that project now works for Bitwarden so there's some risk of a rugpull. Of course it's OSS but you'll need to trust a fork or maintain it yourself if said rugpull happens.

[Snow_Falls]

The maintainer has said that they've been given permission to maintain it in their free time. All it takes is a bad quarter and the CEO decides they don't want to be supporting a competitor and that goes away. It's possible that a community continuation could happen but I wouldn't rely on something so uncertain for something as important as credentials.

[l72]

It’s a bad strategy. I am capable so I host an instance of vaultwarden for myself and spouse (only available via our vpn)

But when friends and family ask for my recommendation I send them to Bitwarden and they pay for the service.

If it wasn’t for vaultwarden and the clients being open source I would not be using it nor recommending it.

I’d probably still be using keepass with manual sync and when friends and family ask for suggestions I’d probably shrug and say I don’t trust any of them.

[giancarlostoro]

Kind of makes a lot of sense that they wound up working there too.

[akerl_]

The expansion of "rugpull" to encompass "a company or open source developer changing the roadmap or level of investment in something they develop" is fascinating.

[wolvoleo]

I think that term refers more to the conflict of interest that now exists.