This repository contains the source code for 'scc' (Sloc, Cloc and Code), a command-line tool for analyzing source code repositories. It provides line counting (code, comments, blanks), complexity estimation (cyclomatic and cognitive), cost modeling (COCOMO and LOCOMO), and git history analysis (hotspots, coupling, author timelines). The tool supports multiple output formats (tabular, JSON, CSV, HTML, etc.) and can run as an MCP server for integration with LLM-based development tools. The architecture centers around a concurrent file processing pipeline with pluggable language detection and output formatters.
Gitlogue is a terminal-based Git history visualizer that replays commits as a cinematic typing animation with syntax highlighting. It loads a local Git repository, extracts diffs, and renders the changes character by character in a split-pane terminal interface (ratatui). The core architecture is a monolithic Rust binary using clap for CLI, git2 for Git operations, tree-sitter for syntax highlighting across 32 languages, and crossterm for terminal I/O. It supports multiple playback modes (random, chronological, watch) and includes a configuration system, 17 built-in themes, and a custom animation engine with step-based simulation and checkpoint/restore. Notable reusable components include the SelectableParagraph widget (isolated ratatui component for text selection and dimming) and the Theme system (extensible struct with ~40 named colors). The codebase is well-structured but exhibits moderate technical drift risk due to heavy tree-sitter dependency chain, rapid feature growth, and potential staleness with some language grammare updates. CI/CD is active but the release workflow is manual. Overall, gitlogue is a solid, professional terminal application that effectively delivers its claimed functionality.
This repository is a git mirror of the Emacswiki, containing the full version history of all wiki pages and uploaded files (primarily Emacs Lisp libraries) since August 2009. It is updated regularly via pushes from the Oddmuse wiki engine. There are no source code files or data pipelines; the entire content is a historical collection of wiki edits stored as text files in a git repository. The repository serves as an offline archive and version history for the Emacswiki community. While it is not a typical software or data science project, it is well-maintained and reliable for browsing or analyzing the wiki's history.