Show HN: EnvKey – securely manage API keys, credentials, and config

Re:Show HN: EnvKey – securely manage API keys, credentials, ... by koolba on Monday September 25, 2017 @05:44PM (#15334446)

In the same vein, why should the client be closed sourced at all?

I skimmed through the source of the npm package and see that it's a shim for a binary blob for each target environment (linux32, linux64, windows, etc). It's 8MB per platform and the tarball has all the other platforms there as well so there's 52MB of junk added to each app build:

    $ du -h node_modules/envkey
    6.7M	node_modules/envkey/ext/envkey-fetch_1.0.0_windows_386
    6.8M	node_modules/envkey/ext/envkey-fetch_1.0.0_freebsd_386
    6.8M	node_modules/envkey/ext/envkey-fetch_1.0.0_darwin_386
    8.2M	node_modules/envkey/ext/envkey-fetch_1.0.0_linux_amd64
    8.1M	node_modules/envkey/ext/envkey-fetch_1.0.0_windows_amd64
    6.8M	node_modules/envkey/ext/envkey-fetch_1.0.0_linux_386
    8.2M	node_modules/envkey/ext/envkey-fetch_1.0.0_darwin_amd64
    8.2M	node_modules/envkey/ext/envkey-fetch_1.0.0_freebsd_amd64
    60M	node_modules/envkey/ext
    8.0K	node_modules/envkey/__tests__
    60M	node_modules/envkey

[ Parent | on HN ]

Re:Show HN: EnvKey – securely manage API keys, credentials, ... by danenania on Monday September 25, 2017 @05:54PM (#15334507)

All the clients (including the app) are fully open-source. Both the npm package and the ruby gem wrap a lower-level library that is written in Go - https://github.com/envkey/envkey-fetch. This implements core OpenPGP logic in a cross-platform way. I'll try to make this clearer in the Readme.

I could also look at splitting out platform-specific packages for those who only need a subset of them, but the reason for including every binary is to make it plug-and-play for multi-platform teams.

[ Parent | on HN ]