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

Enable dependency vulnerability scanning #1421

Open
Fraserhardy opened this issue Jul 18, 2022 · 1 comment
Open

Enable dependency vulnerability scanning #1421

Fraserhardy opened this issue Jul 18, 2022 · 1 comment

Comments

@Fraserhardy
Copy link
Contributor

In order to ensure the framework is using libraries that do not contain vulnerabilities, it would help to have the framework scanned automatically.

Due to the non-standard nature of dependency handling in Play 1 this is more difficult, however I have found that its possible with Snyk using their "scan unmanaged jar" feature: https://docs.snyk.io/snyk-cli/test-for-vulnerabilities/scan-all-unmanaged-jar-files

@cies
Copy link
Contributor

cies commented Sep 9, 2024

When we at RePlay upload to OSSHR (Maven Central) we get a vulnerability scan on the dependencies by SonaType for free by email (with a link to see the details). I think this is based on the JAR, not on the dependency specification; you could ask the Play1 devs if they also get this report and if they can publish it or share it with you.

Since the RePlay project uses Gradle, instead of the "ivy2-situation" Play1 has, we can also do dependency vulnerability scans based on that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants