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
What's the problem this feature will solve?
Provide information about security vulnerabilities of PyPI packages.
Describe the solution you'd like
I suggest adding links on project detail pages to the packages' pages on the Snyk Advisor website. The most basic implementation would be to add a link in the sidebar, alongside the existing link to the libraries.io page.
Snyk Advisor pages include security information about packages, both summarized and in detail, as well as other useful info and stats.
For example: The package detail page for networkx would include an additional link to its Snyk Advisor page. This page currently prominently displays a red "SECURITY ISSUES FOUND" label for the latest version of networkx, with details (high severity!) and links to more information in the "Security" section of the page. (For future reference, here's an archived version from today on the Internet Archive Wayback Machine.)
Additional context
Packaging tools in some other programming ecosystems have begun providing security information about packages. One prominent example of this is npm, whose CLI tool began showing warnings for installed packages with known security vulnerabilities. The availability of tooling and information for Python packages is only recently becoming available, but awareness in the community is still low. Adding this to PyPI could help a great many projects and people discover and address security issues much earlier.
Full disclosure: I worked for a while developing Snyk Advisor as a contractor. I'm no longer affiliated with Snyk in any way, and have no direct or potential financial interest in their services being used or succeeding. Snyk did reach out to ask what I thought about this and whether I'd be willing to suggest this publicly, which I'm happy to do with no compensation of any sort, simply because I think it will benefit the community.
The text was updated successfully, but these errors were encountered:
I'd definitely give it the thumbs up!
As a data engineering team lead I find myself many times emphasize to my team members, the importance of some background check of a python package, before they just throw it into our requirements.txt files.
Specifically, I instruct them to check in Snyk Advisor as part of some other examinations.
It is a great idea to put all in one place, an PyPi is exactly the right place for it!
👍👍👍
Uh oh!
There was an error while loading. Please reload this page.
What's the problem this feature will solve?
Provide information about security vulnerabilities of PyPI packages.
Describe the solution you'd like
I suggest adding links on project detail pages to the packages' pages on the Snyk Advisor website. The most basic implementation would be to add a link in the sidebar, alongside the existing link to the libraries.io page.
Snyk Advisor pages include security information about packages, both summarized and in detail, as well as other useful info and stats.
For example: The package detail page for networkx would include an additional link to its Snyk Advisor page. This page currently prominently displays a red "SECURITY ISSUES FOUND" label for the latest version of networkx, with details (high severity!) and links to more information in the "Security" section of the page. (For future reference, here's an archived version from today on the Internet Archive Wayback Machine.)
Additional context
Packaging tools in some other programming ecosystems have begun providing security information about packages. One prominent example of this is npm, whose CLI tool began showing warnings for installed packages with known security vulnerabilities. The availability of tooling and information for Python packages is only recently becoming available, but awareness in the community is still low. Adding this to PyPI could help a great many projects and people discover and address security issues much earlier.
Full disclosure: I worked for a while developing Snyk Advisor as a contractor. I'm no longer affiliated with Snyk in any way, and have no direct or potential financial interest in their services being used or succeeding. Snyk did reach out to ask what I thought about this and whether I'd be willing to suggest this publicly, which I'm happy to do with no compensation of any sort, simply because I think it will benefit the community.
The text was updated successfully, but these errors were encountered: