Could sec:java-sec-code:1.0.0 drop off redundant dependencies?#75
Closed
slimming-fat wants to merge 1 commit intoJoyChou93:masterfrom
Closed
Could sec:java-sec-code:1.0.0 drop off redundant dependencies?#75slimming-fat wants to merge 1 commit intoJoyChou93:masterfrom
slimming-fat wants to merge 1 commit intoJoyChou93:masterfrom
Conversation
Owner
|
Thanks for the pr, but don't want to deal with that. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi, I found that sec:java-sec-code:1.0.0’s pom file introduced 199 dependencies. However, among them, 8 libraries (4% have not been used by your project), the redundant dependencies are listed below.
More seriously, 8 redundant libraries have not been maintained by developers for more than 3 years (outdated dependencies).
Reduce these unused dependencies can help prevent introducing bugs/vulnerabilities from dependencies with outdated. Meanwhile, it can minimize the project size. To safely remove redundant dependencies, I constructed a complete call graph (resolved most of Java reflection and dynamic binding), and validated that they have not been used by the client code.
This PR sec:java-sec-code:1.0.0 for removing the redundant dependencies have passed the tests.
Best regards
Redundant dependencies
Redundant indirect dependencies:
Outdated dependencies
xml-apis:xml-apis:1.4.01 (4260 days without maintenance)
org.codehaus.mojo:animal-sniffer-annotations:1.14 (2974 days without maintenance)
com.google.errorprone:error_prone_annotations:2.0.18 (2240 days without maintenance)
com.google.code.findbugs:jsr305:1.3.9 (4985 days without maintenance)
net.bytebuddy:byte-buddy:1.8.12 (1789 days without maintenance)
org.mapstruct:mapstruct:1.2.0.Final (2009 days without maintenance)
com.ibm.icu:icu4j:4.6 (4520 days without maintenance)
com.google.j2objc:j2objc-annotations:1.1 (2281 days without maintenance)