Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #90495 > unrolled thread
| Started by | Mark Lawrence <breamoreboy@yahoo.co.uk> |
|---|---|
| First post | 2015-05-12 22:17 +0100 |
| Last post | 2015-05-12 22:17 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Suggestion: PEP for tracking vulnerable packages within PyPI Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-05-12 22:17 +0100
| From | Mark Lawrence <breamoreboy@yahoo.co.uk> |
|---|---|
| Date | 2015-05-12 22:17 +0100 |
| Subject | Re: Suggestion: PEP for tracking vulnerable packages within PyPI |
| Message-ID | <mailman.419.1431465458.12865.python-list@python.org> |
On 12/05/2015 20:46, Grant Murphy wrote: > Hi, > > When pulling in a dependency via pip it is currently difficult to reason about > whether there are any vulnerabilities associated with the package version you > are using. I think the Python package management infrastructure could be > extended to facilitate this capability reasonably easily. PyPI already > contains a lot of metadata around package owners and releases available. > Adding the ability to flag a release as having a vulnerability and CVE > associated with it seems like a reasonable addition to me. > > Currently there are some projects that are trying to track this information [1], > however by including this type of information as a part of the main Python > infrastructure I think it would encourage better vulnerability management > practices within the community. > > I'd like some feedback on how to move forward with this suggestion. Does > this seem like something that could be worth turning into a PEP? > > 1. https://github.com/victims/victims-cve-db > > - Grant > It strikes me as a great idea. As you've got the time to send three emails some 40 minutes apart saying the same thing, you must have the time to do the work that is involved, so please let us know what your plans are. -- My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language. Mark Lawrence
Back to top | Article view | comp.lang.python
csiph-web