pipenv: Your API Key is invalid
$ pipenv check
Checking PEP 508 requirements…
Passed!
Checking installed package safety…
An error occurred:
Your API Key '1ab8d58f-5122e025-83674263-bc1e79e0' is invalid. See https://goo.gl/O7Y1rS
2020-04-11T10:08:05-0700 exit 1
I can provide pipenv --support if necessary.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 98
- Comments: 27 (5 by maintainers)
Commits related to this issue
- Use 'safety' (which is the free 1month delayed vulnerability database) instead of pipenv. Pipenv is borking out because it depends on an expired api key. See https://github.com/pypa/pipenv/issues/41... — committed to APrioriInvestments/typed_python by braxtonmckee 4 years ago
- Fix failing pyup API key - Update vendored safety package - Swap to blank pyup API key by default (but allow custom key) - Slightly improve safety revendoring - Fixes #4188 Signed-off-by: Dan Ryan <... — committed to pypa/pipenv by techalchemy 4 years ago
- travis: set blank PIPENV_PYUP_API_KEY workaround for `pipenv check` pyup.io safety check. pyup.io recently removed the requirement for a custom API key for pipenv's safety check, and, until an upstr... — committed to tjresearch/research-theo_john by theo-o 4 years ago
- chore: pipenv check workaround https://github.com/pypa/pipenv/issues/4188 PIPENV_PYUP_API_KEY= can be removed when pipenv-2020.X.X is released — committed to jdobes/vulnerability-engine by jdobes 4 years ago
- chore: pipenv check workaround https://github.com/pypa/pipenv/issues/4188 PIPENV_PYUP_API_KEY= can be removed when pipenv-2020.X.X is released — committed to jdobes/vmaas by jdobes 4 years ago
- chore: pipenv check workaround https://github.com/pypa/pipenv/issues/4188 PIPENV_PYUP_API_KEY= can be removed when pipenv-2020.X.X is released — committed to RedHatInsights/vulnerability-engine by jdobes 4 years ago
- chore: pipenv check workaround https://github.com/pypa/pipenv/issues/4188 PIPENV_PYUP_API_KEY= can be removed when pipenv-2020.X.X is released — committed to RedHatInsights/vmaas by jdobes 4 years ago
- fix safety check (https://github.com/pypa/pipenv/issues/4188) needed until new release of pipenv — committed to enioka-Haute-Couture/pyoupyou by bport 4 years ago
- chore: pipenv check workaround https://github.com/pypa/pipenv/issues/4188 PIPENV_PYUP_API_KEY= can be removed when pipenv-2020.X.X is released — committed to RedHatInsights/vmaas by jdobes 4 years ago
- chore: pipenv check workaround https://github.com/pypa/pipenv/issues/4188 PIPENV_PYUP_API_KEY= can be removed when pipenv-2020.X.X is released — committed to RedHatInsights/vmaas by jdobes 4 years ago
- Merge tag 'v2020.5.28' of github.com:pypa/pipenv 2020.5.28 (2020-05-28) ====================== Features & Improvements ----------------------- - `pipenv install` and `pipenv sync` will no longer ... — committed to fwojciak/pipenv by deleted user 4 years ago
- chore: pipenv check workaround https://github.com/pypa/pipenv/issues/4188 PIPENV_PYUP_API_KEY= can be removed when pipenv-2020.X.X is released — committed to jdobes/vulnerability-engine by jdobes 4 years ago
- chore: pipenv check workaround https://github.com/pypa/pipenv/issues/4188 PIPENV_PYUP_API_KEY= can be removed when pipenv-2020.X.X is released — committed to jdobes/vulnerability-engine by jdobes 4 years ago
- chore: pipenv check workaround https://github.com/pypa/pipenv/issues/4188 PIPENV_PYUP_API_KEY= can be removed when pipenv-2020.X.X is released — committed to RedHatInsights/vulnerability-engine by jdobes 4 years ago
@Jwomers is now taking care of pyup.io with the help of @harlekeyn and @rafaelpivato. ccd
After a brief conversation with the new pyup.io management, (and it seems others have observed this already) we won’t need the API key anymore to connect with pyup.io. So we will remove the API key. In the meantime I believe this can be resolved by simply setting the environment variable
PIPENV_PYUP_API_KEY="".WORKAROUND for those who cannot upgrade:
I don’t want to to tell the maintainers how to handle issues and fixes, but maybe keep issues open until a fix is actually released. This closed issue gives the impression that the problem has been fixed, even though it has only been merged into master, but not yet released.
A workaround is to install safety and use
safety checkinstead ofpipenv check.pipenv checkworks correctly for me when usingpipenv-2020.4.1b1, installed through:on a macOS system.
@kristang pipenv check was actually working in last 2 weeks using the old pipenv version, but here we go again…
I can’t speak for @jdobes, but I have a build pipeline, using pipenv 2018.11.26, that runs (at least) nightly. I never applied the environment variable work-around, and have successful runs from April 24 to May 2. On May 2nd it started failing with this issue.
Just wanted to share more information …
pipenv lock --requirements | safety check --stdin