cafecompare | Java code comparison tool

by GraxCode Java Version: 1.3.1 License: GPL-3.0

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | cafecompare Summary

cafecompare is a Java library. cafecompare has no bugs, it has no vulnerabilities, it has build file available, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

Cafecompare is a GUI application for analysis and comparison of java archives and class files. Similar to github commits the file diffs are highlighted. Also works with obfuscated code. Cafecompare is the first tool ever to support remapping class names of an obfuscated jar archive by similarity to the other jar archive (with libraries or an old source file, where mappings can be taken from). This introduces a new era of deobfuscation.

Support

Quality

Security

License

Reuse

Support

cafecompare has a low active ecosystem.

It has 223 star(s) with 22 fork(s). There are 6 watchers for this library.

It had no major release in the last 12 months.

There are 0 open issues and 2 have been closed. On average issues are closed in 4 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of cafecompare is 1.3.1

Quality

cafecompare has 0 bugs and 0 code smells.

Security

cafecompare has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

cafecompare code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

cafecompare is licensed under the GPL-3.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

cafecompare releases are available to install and integrate.

Build file is available. You can build the component from source.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi has reviewed cafecompare and discovered the below as its top functions. This is intended to give you an instant insight into cafecompare implemented functionality, and help decide if they suit your requirements.

Initialize the menu
Replace mappings between two classes
Finds the common code between two classes
Save a class file to a file
Visits the annotation
Appends a string representation of the given access flags
Generate the class descriptor
Appends a string representation of the given access flags
Merge a set of patches
Recursively split a list of patches
Print a local variable annotation
Generate the provide descriptor
Compute a list of Diff objects from text1 and text2
Generate invoke instruction
Process a method
Output field
Process a local variable
Converts a Diff object into a pretty HTML report
Decompile a byte array
Moves a tree item
Set the icon
Converts a list of Diff objects to a string
Generate a lookup switch instruction
Highlights a search text
Parses a text line and returns a list of patches
Reverses the method mapping between two methods
Decompiles a byte array

Get all kandi verified functions for this library.

cafecompare Key Features

No Key Features are available at this moment for cafecompare.

cafecompare Examples and Code Snippets

No Code Snippets are available at this moment for cafecompare.

Community Discussions

No Community Discussions are available at this moment for cafecompare.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install cafecompare

To compare two jar archives or two classes, you have to add them to the trees on the left. On the top goes the old jar file, on the bottom the new version. The left side of the decompiler panel will show the old code, the right side the new code. Deleted code will be marked with red color in the left panel, inserted code will be green in the right panel. If you want to remap class files by similarity, make sure the obfuscated file is placed in the bottom tree, and the (unobfuscated) source file in the top one. Be aware that this could take VERY long! Have fun comparing and deobfuscating!.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: