Open Source Unix Shell Source Code Analysis Tools

Hack includes monospaced regular, bold, italic, and bold italic sets to cover all of your syntax highlighting needs. Over 1500 glyphs that include lovingly tuned extended Latin, modern Greek, and Cyrillic character sets. Powerline glyphs are included in the regular set. Patching is not necessary. Install and go. No frills. No gimmicks. Hack is hand groomed and optically balanced to be your go-to code face. Type design features to improve legibility in the harsh conditions of the screen. A libre typeface with generous licensing that permits modification & commercial use. Hack has deep roots in the libre, open source typeface community and includes the contributions of the Bitstream Vera & DejaVu projects. The face has been re-designed with an expanded glyph set, modifications of the original glyph shapes, and meticulous attention to metrics.

This repository is for the GitHub Action to run a Super-Linter. It is a simple combination of various linters, written in bash, to help validate your source code. The super-linter finds issues and reports them to the console output. Fixes are suggested in the console output but not automatically fixed, and a status check will show up as failed on the pull request. The design of the Super-Linter is currently to allow linting to occur in GitHub Actions as a part of continuous integration occurring on pull requests as the commits get pushed. It works best when commits are being pushed early and often to a branch with an open or draft pull request. There is some desire to move this closer to local development for faster feedback on linting errors but this is not yet supported. There is no need to set the GitHub Secret as it is automatically set by GitHub, it only needs to be passed to the action.

Cov is a code coverage tool to get your code coverage after your runuing some steps for your programs.It is based on llvm(Low Level Virtual Machine,http://llvm.org/).Now,it's only a begining,so welcome anybody to join in.

Often I have seen some Huge Maintenance Projects it is always very difficult to track the incremental files for each release and If we want to do that we need to checkout both the branches and use some UI based tool to get the diff of the files finally we end up waiting in front of the PC for a long time and do this job. In many cases we spend more than 2 hrs/day. The time increases if there are more such parallel releases and at the end of the day 1 developer does it as full time job and has zero productivity. I thought of adding value here. This just gets the diff files. Can be used for Static code analysis like PMD to do PMD only for the delta. The current status of the project is in Development". If you wish to add something please mail me.

It's a web application which provides a unify solution to stat. CVS/SVN repository modules code change information and generate html reports. User can browse line of change, file of change, code diff, check-in comment and so on, it can stat. more repository modules one time. After repository modules configured, stat. is simple like a search.

It's a web application which provides a unify solution to stat. CVS/SVN repository modules code change information and generate html reports. User can browse line of change, file of change, code diff, check-in comment and so on, it can stat. more repository modules one time. After repository modules configured, stat. is simple like a search. It's the mirror project of CodeChangeViewer: http://sourceforge.net/projects/ccv/.

These bash shell scripts are intended to iteratively load executable files via symbolic links and echo output to a log file for later review. These bash shell scripts rely on a directory structure intended to group testing and reporting executable files by project, target platform, and version.

Utility to fix common misspellings, typos in source codes. There are lots of typical misspellings in program codes. Typically they are more eye-catching in the living code but they can easily hide in comments, examples, samples, notes and documentations. With this utility you can fix a large number of them very quickly. Be aware that the utility does not check or fix file names. It can easily happen that a misspelled word is fixed in a file name in a program's code, but the file itself will not be renamed by this utility. And also important to note to be extra careful when fixing public APIs! A manual review is always needed to verify that nothing has been broken.

The 'pysourceinfo' package provides source information on Python runtime objects based on 'inspect', 'sys', 'os', and 'imp'. The covered objects include packages, modules, functions, methods, scripts, and classes by two views: - File System View - packages, modules, and linenumbers - based on files and paths - Runtime Object View - callables, classes, and containers - based on in-memory RTTI / introspection The supported platforms are: - Linux, BSD, Unix, OS-X, Cygwin, and Windows - Python2, Python3 - CPython, PyPy Object addresses within modules - Object Identifier OID - and the display of the runtime call flow are supported by 'PyStackInfo'. Online documents: https://pysourceinfo.sourceforge.io/