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

DOC: Public instance of PurlDB and Vulnerable Code - ToS and Data Privacy? #195

Open
ghsa-retrieval opened this issue Nov 13, 2024 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@ghsa-retrieval
Copy link

What type of documentation would you like?
Details on integration of PurlDB and Vulnerable Code: https://dejacode.readthedocs.io/en/latest/application-settings.html

Documentation topic
When running DejaCode it by default connects to public instances of PurlDB and Vulnerable Code. It is unclear when we are permitted to use these (testing, non-commercial, commercial) in our own deployment of DejaCode and what kind of data is being transmitted.

@ghsa-retrieval ghsa-retrieval added the documentation Improvements or additions to documentation label Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants