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

Update pipenv check docs for Safety-DB removal #1749

Merged
merged 2 commits into from
Mar 15, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions docs/advanced.rst
Original file line number Diff line number Diff line change
Expand Up @@ -187,12 +187,13 @@ Example::

.. note::

Commercial redistributors of `pipenv` should be aware that the public `Safety-DB`
project backing this feature is licensed as CC-BY-NC-SA by `pyup.io`. While
`pyup.io` have [stated explicitly](https://github.com/pypa/pipenv/issues/1651#issuecomment-372583779)
that commercial *use* of this `pipenv` feature is fine, commercial redistributors may want
to perform their own legal assessment and perhaps chat directly to `pyup.io` about
the specific licensing terms.
In order to enable this functionality while maintaining its permissive
copyright license, `pipenv` embeds an API client key for the backend
Safety API operated by pyup.io rather than including a full copy of the
CC-BY-NC-SA licensed Safety-DB database. This embedded client key is
shared across all `pipenv check` users, and hence will be subject to
API access throttling based on overall usage rather than individual
client usage.


☤ Community Integrations
Expand Down