Technology

59534 readers

3223 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

627

Concerns Raised Over Bitwarden Moving Further Away From Open-Source (www.phoronix.com)

submitted 1 month ago by AsudoxDev@programming.dev to c/technology@lemmy.world

203 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] coolmojo@lemmy.world 3 points 1 month ago (1 children)

I was referring to this which started it all.

[–] sugar_in_your_tea@sh.itjust.works 5 points 1 month ago

Here is the code in question. Basically, it's a source-available, but not FOSS internal SDK, with the following language:

The password manager SDK is not intended for public use and is not supported by Bitwarden at this stage. It is solely intended to centralize the business logic and to provide a single source of truth for the internal applications. As the SDK evolves into a more stable and feature complete state we will re-evaluate the possibility of publishing stable bindings for the public. The password manager interface is unstable and will change without warning.

So I think the "bug" here is in not linking the original repo in the NPM package, and there's a decent chance that this internal SDK will become FOSS in the future once it stabilizes. That said, it's currently not FOSS, but it's too early IMO to determine whether Bitwarden is moving in a non-FOSS direction, or if they're just trying to keep things simple while they do some heavy refactoring to remove redundancy across apps.

Given their past, I'm willing to give them the benefit of the doubt, but I'll be making sure I have regular backups in case things change.