tornadory/monodroid-samples
A collection of Xamarin.Android sample projects.
Public GitHub Catalog
Discovered Oct 18, 2026
tornadory / PyChecker
PyChecker is a static analysis tool for finding bugs in Python source code. It finds problems that are typically caught by a compiler for less dynamic languages, like C and C++. It is similar to lint. This is my mirror/fork of the SourceForge CVS repository.
About this discovery
Public repository record indexed from GitHub. Explore verified star velocity metrics, source code repositories, and curated developer tool directories across the GitHubRepo ecosystem.
#39358821GitHub System ID
tornadoryOrganization / User
PublicVisibility
ActiveCatalog Status
More from tornadory
tornadory/Gagawa
The aim of this project is to use static and dynamic analysis on the open-source project called 'Gagawa'. Static analysis was performed using tools like Findbugs, PMD, SonarQube. Dynamic Analysis was performed by inserting 'asserts' in the Java code and also by writing test cases that could trigger the asserts.
tornadory/PyChecker-1
PyChecker is a static analysis tool for finding bugs in Python source code. It finds problems that are typically caught by a compiler for less dynamic languages, like C and C++. It is similar to lint. This is my mirror/fork of the SourceForge CVS repository.
tornadory/reclipse-emf
Reclipse is a reverse engineering tool for the automatic detection of patterns in source code. A pattern is a general, reusable solution to a commonly occurring problem in software design. Detecting pattern occurrences can help understand a piece of code and thereby provide deeper insight into a software. Reclipse provides a static and a dynamic pattern detection. The static analysis in Reclipse uses a pattern specification language based on object diagrams, the so-called structural patterns. The static analysis requires the source code of the software system and a library of structural patterns. An inference algorithm recovers the structure of design patterns by graph matching. It results in an annotated class diagram which shows the possible implementations of design patterns, so-called pattern candidates. A following dynamic analysis can be used to reject or confirm these pattern candidates. For this purpose the candidates’ behavior can be monitored during the program execution, using the Reclipse tracer. The tracer generates a number of traces for each candidate.