kelinci | AFL-based fuzzing for Java | Testing library

by isstac Java Version: Current License: Apache-2.0

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

kandi X-RAY | kelinci Summary

kelinci is a Java library typically used in Testing applications. kelinci has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However kelinci build file is not available. You can download it from GitHub.

AFL-based fuzzing for Java

Support

Quality

Security

License

Reuse

Support

kelinci has a low active ecosystem.

It has 171 star(s) with 45 fork(s). There are 10 watchers for this library.

It had no major release in the last 6 months.

There are 4 open issues and 8 have been closed. On average issues are closed in 34 days. There are 5 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of kelinci is current.

Quality

kelinci has 0 bugs and 0 code smells.

Security

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

kelinci code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

kelinci is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

kelinci releases are not available. You will need to build from source code and install.

kelinci has no build file. You will be need to create the build yourself to build the component from source.

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

kelinci saves you 343 person hours of effort in developing the same functionality from scratch.

It has 822 lines of code, 48 functions and 10 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

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

Command - line tool
Load a directory
Adds a file to a JAR
Load classes from the classpath
Write a class to a file
Extract class files from a JAR file
Returns the input files from the classpath
Adds an URL to the classpath
Simple test parser
Determine the z of the next path
Handle a table switch
Entry point for testing
Handle a Fuzzer run
Starts the server process
Creates the output jar file
Creates a directory in JAR
Main method for debugging
Tries to read an image
Visits a method

Get all kandi verified functions for this library.

kelinci Key Features

No Key Features are available at this moment for kelinci.

kelinci Examples and Code Snippets

No Code Snippets are available at this moment for kelinci.

Community Discussions

Trending Discussions on kelinci

How to get data from localstorage into text field without button

QUESTION

How to get data from localstorage into text field without button

Asked 2021-Jun-01 at 16:11

I have some problems to trying get array data from local storage to textfield. can some one help me ?

...

ANSWER

Answered 2021-Jun-01 at 16:11

What about this one?

Source https://stackoverflow.com/questions/67792083

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

Vulnerabilities

No vulnerabilities reported

Install kelinci

The application has two components. First, there is a C application that acts as the target application for AFL. It behaves the same as an application built with afl-gcc / afl-g++; AFL cannot tell the difference. This C application is found in the subdirectory 'fuzzerside'. It sends the input files generated by AFL to the JAVA side over a TCP connection. It then receives the results and forwards them to AFL in its expected format. To build, run make in the 'fuzzerside' subdirectory. The second component is on the JAVA side. It is found in the 'instrumentor' subdirectory. This component instruments a target application with AFL style administration, plus a component to communicate with the C side. When later executing the instrumented program, this sets up a TCP server and runs the target application in a separate thread for each incoming request. It sends back an exit code (success, timeout, crash or queue full), plus the gathered path information. Any exception escaping main is considered a crash. To build, run gradle build in the 'instrumentor' subdirectory.

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: