We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello! 👋
Bit of a continuation of #360, but I'd love to find out if normalized_licenses could also get added to a package's versions response.
normalized_licenses
Example:
https://packages.ecosyste.ms/api/v1/registries/npmjs.org/packages/ua-parser-js contains licenses as well as normalized_licenses:
"licenses": "AGPL-3.0-or-later", "normalized_licenses": ["AGPL-3.0-or-later"],
In a previous version they did however use other licenses (MIT, GPLv2) but that can't be read in its normalized format from https://packages.ecosyste.ms/api/v1/registries/npmjs.org/packages/ua-parser-js/versions/0.7.1:
"licenses": "GPLv2,MIT"
It would be great if normalized licenses could get added to this endpoint as well! 🙏
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello! 👋
Bit of a continuation of #360, but I'd love to find out if
normalized_licenses
could also get added to a package's versions response.Example:
https://packages.ecosyste.ms/api/v1/registries/npmjs.org/packages/ua-parser-js contains licenses as well as normalized_licenses:
In a previous version they did however use other licenses (MIT, GPLv2) but that can't be read in its normalized format from https://packages.ecosyste.ms/api/v1/registries/npmjs.org/packages/ua-parser-js/versions/0.7.1:
It would be great if normalized licenses could get added to this endpoint as well! 🙏
The text was updated successfully, but these errors were encountered: