This package is archived upstream:

https://github.com/henrybear327/go-proton-api

On the surface, it seems like a bad idea to ship this in forky.  Is
there any motivation for that?

It seems to be a stale (2 commits) fork of

https://github.com/ProtonMail/go-proton-api

The motivation for the fork appears to be driven by this upstream
project:

https://github.com/henrybear327/Proton-API-Bridge

However that has also been archived.

Let's look into how we can untangle the reverse dependencies to not use
this package, and replace it with a maintained fork.

/Simon

github.com/henrybear327/go-proton-api is superseded by
github.com/rclone/go-proton-api

It is used by rclone.

It (they) are a deliberate fork of github.com/ProtonMail/go-proton-api
that maintains compatibility with rclone. Their intention is to
ultimately push needful patches back to go-proton-api upstream but the
goal of dropping the fork (rclone, not henrybear327) is not reached
yet.

golang-github-henrybear327-go-proton-api can be removed once
golang-github-rclone-go-proton-api is operational.

The same arguments apply to
golang-github-henrybear327-proton-api-bridge superseded by
golang-github-rclone-proton-api-bridge