You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why these changes are being introduced:
As of pipenv 2025.0.1 the use of `pipenv check` would throw
an error, indicating that the library `safety` was not installed.
It worked to run `pipenv check --auto-install` which would
temporarily install `safety`, but this was not ideal for multiple
reasons.
First, we anticipate potentially moving away from `pipenv`.
Second, it appears that `safety` is moving to a pay / subscription
model.
Third, it remains a little obfuscated what `pipenv check` is actually
doing.
As this new situation affects all builds in Github Actions CI,
we need a way to scan for vulnerabilities that ideally is not
a massive overhaul of our vulnerability scanning approach.
How this addresses that need:
`pip-audit` is a nice standalone, open-source library that
performs very similar work to `safety`.
This commit replaces `pipenv check` (which was `safety` under
the hood) with `pip-audit`.
Side effects of this change:
* Builds will be successful in Github Actions
Relevant ticket(s):
* https://mitlibraries.atlassian.net/browse/IN-1240
0 commit comments