Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Consider replacing json-stable-stringify to fulfill compliance for commercial products #494

Open
mapero opened this issue Oct 9, 2023 · 0 comments

Comments

@mapero
Copy link

mapero commented Oct 9, 2023

Hello

This is kind of a feature request. This library directly depends on json-stable-stringify, which depends on jsonify, which has no license and thus cause problems with corporations, at least outside US. See: https://en.wikipedia.org/wiki/Public-domain_software .

Requests to set jsonify under a proper license are not considered: ljharb/jsonify#2 .
An explicit request to allow the usage of jsonify in a commercial product was not given by the author.

There are many alternatives to json-stable-stringify which have proper licenses, such as:

It would be great if you could switchover to one of these alternatives.
This would make your library and also others that depend on you, e.g. swagger-ui usable in commercial products.

Thanks.

Best regard
Jochen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant