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
According to #1384 (comment), license for https://github.com/vmware/photon/wiki/Security-Advisories has been updated in the page.
I wanted to clarify about the json advisories present at https://packages.vmware.com/photon/photon_cve_metadata/, are they under the same license as https://github.com/vmware/photon/wiki/Security-Advisories ?
aboutcode-org/vulnerablecode#36
git clone https://github.com/vmware/photon.wiki.git Pro: Good license. Cons: Does not give json advisories. It gives markdown files. Hassle to parse.
https://packages.vmware.com/photon/photon_cve_metadata/ Pro: Gives json, structured to parse Cons: License not explicitly mentioned
Kindly clarify if both https://github.com/vmware/photon/wiki/Security-Advisories and https://packages.vmware.com/photon/photon_cve_metadata/ are under the same license.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
According to #1384 (comment), license for https://github.com/vmware/photon/wiki/Security-Advisories has been updated in the page.
I wanted to clarify about the json advisories present at https://packages.vmware.com/photon/photon_cve_metadata/, are they under the same license as https://github.com/vmware/photon/wiki/Security-Advisories ?
aboutcode-org/vulnerablecode#36
Describe the solution you'd like
Kindly clarify if both https://github.com/vmware/photon/wiki/Security-Advisories and https://packages.vmware.com/photon/photon_cve_metadata/ are under the same license.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: