4 ms·
Am I allowed to make a subscription url publically available? Say I write a package which has a paywalled package as a dependency. If I want to publish MY packa
by Null-Set 7y ago
Am I allowed to make a subscription url publically available? Say I write a package which has a paywalled package as a dependency. If I want to publish MY package freely on npm under an MIT license, can I pay the subscription fee and commit the resulting fetch-url with my license key into github, and transitivly allow users of my package to use the paywalled package?
- krapht 7y agoI hope not. That would go against this project's purpose of trying to find a funding model for popular, transitively-used packages.
- sdrzn 7y agoIf the transitive project's owner agrees to letting anyone use your license key freely, we can certainly do this. However I recommend setting up your own project on GitRoyalty since we automatically replace your license key with a bundle identifier (i.e. bundle:<repo>). This way, before users can download your project, we confirm their IP addresses are associated with active subscriptions to all your transitive dependencies. I wrote a bit more about transitive dependencies here: https://gitroyalty.com/docs/faq/how-do-transitive-dependencies-work https://gitroyalty.com/docs/faq/how-do-transitive-dependenci...