Skip to content
This repository has been archived by the owner on Jun 27, 2019. It is now read-only.

Why is zapier-platform-core UNLICENSED? #318

Closed
wking opened this issue May 14, 2018 · 1 comment
Closed

Why is zapier-platform-core UNLICENSED? #318

wking opened this issue May 14, 2018 · 1 comment

Comments

@wking
Copy link
Contributor

wking commented May 14, 2018

Here's its package.json entry. According to the npm docs, that means:

... you do not wish to grant others the right to use a private or unpublished package under any terms

That puts all Zapier apps (who will depend on the core package and download it as a part of npm install) in a questionable legal state. Could you consider adopting a license for the core project? Even if it's something like:

Everyone is permitted to copy and distribute verbatim copies of this package, but changing it is not allowed.

EDIT: zapier-platform-cli is also UNLICENSED, and probably needs a license as well to allow folks to install and run it locally.

@xavdid
Copy link
Contributor

xavdid commented May 29, 2019

My understanding is that this is intentional. This was the answer elsewhere:

We're not planning on placing any of the standard open source licenses on our platform cli, core, schema, etc. repositories.

Right now the intention is that you are welcome to freely use our unlicensed repositories in the normal lifecycle of developing an integration with Zapier (which includes any CI, deployment processes, test harnesses, etc.) as outlined in our developer terms of service, but not for anything else outside of that.

additionally, the open source libraries are covered under our platform terms: https://zapier.com/platform/tos

@xavdid xavdid closed this as completed May 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants