maltego-trx is the legacy Python SDK for building Maltego transforms (the OSINT/graph investigation platform), now explicitly archived and superseded by the actively maintained maltego-transforms SDK. In production it runs as a Flask HTTP server: the Maltego desktop client POSTs an XML transform request to /run/<transform_name>/, the server parses it into a MaltegoMsg, dispatches to a registered transform class, and serializes the resulting MaltegoTransform response back as XML. Transform classes are auto-discovered from the project's local `transforms` package (class name must match the filename and subclass DiscoverableTransform). The package also ships a CLI (`maltego-trx start`/`init`) that scaffolds new transform projects from a template directory, plus a project-level CLI (`project.py runserver/list/local`) implemented in handler.py.
TileMapLayer3D is a Godot 4 editor plugin (addon) that provides a custom TileMapLayer3D node for building 3D tile-based levels from 2D tilesheets, inspired by Crocotile3D-style workflows. It is not a standalone game or data project; it is a tool/library that ships editor UI (toolbars, tileset panel, 3D cursor, gizmos), a runtime API for placing/erasing/querying tiles during gameplay, and a demo scene. The plugin supports manual painting, autotile/terrain bitmask placement, animated tiles, area fill/erase, smart select/fill, sculpt brushes, vertex editing, collision baking, and mesh merging, rendering tiles through chunked MultiMesh instancing with custom shaders.
This repository is a collection of automation scripts designed to interact with various consumer services. It includes scripts for automating coupon collection from Meituan food delivery, task completion and reward collection for SF Express loyalty programs, and step count modification for Xiaomi Sports fitness tracking. The scripts are designed to run in automation environments like QingLong and make HTTP requests to service APIs to perform automated actions. A notable component is the notify.py module, which provides a unified interface for sending notifications across multiple platforms (Bark, DingTalk, Feishu, etc.) and can be easily reused in other projects. The code is functional but consists largely of service-specific API interactions with limited abstraction, making most components tightly coupled to specific services.
This repository distributes precompiled binary libraries (static archives) for the ESP32 series WiFi stack, used as a submodule within the Espressif IoT Development Framework (ESP-IDF). It contains no source code for the WiFi stack itself; instead, it provides archived .a files for various ESP32 variants (ESP32, ESP32-S2, ESP32-C3, etc.) and a set of shell scripts and CI configurations to manage library updates, fix symbol collisions (e.g., printf redefinition), and run build and feature tests. The repository acts as a binary release artifact, not a standalone application or library with reusable software components. Its primary purpose is to be checked out as a submodule in ESP-IDF to supply the low-level WiFi, mesh, and networking layers.
UKIKU is a feature-rich Android application for streaming and downloading anime episodes, built primarily in Kotlin with some legacy Java. It scrapes content from animeav1.com (and related sites) using Jsoup and custom JavaScript extraction, bypassing Cloudflare protection via a WebView-based mechanism. The app offers a comprehensive anime tracking experience: browsing a directory, searching, viewing details, watching episodes via ExoPlayer (with Chromecast and Android TV support), downloading (including HLS), managing favorites and watch history, queuing episodes, earning achievements, and syncing user data to Firebase Firestore or Dropbox. It also includes a gamified economy system (loli-coins) and extensive ad integration (AdMob, AppLovin). The architecture follows MVVM with Room database, WorkManager, and coroutines, but suffers from significant technical debt: duplicate UI layouts (material vs. non-material), deprecated libraries (Anko, RxJava, old MaterialDialogs), fragile scraping logic, weak encryption, and hardcoded API keys. Despite these issues, the app is functional and has a large user base (203 stars, 39 forks). It is not a data research project; it is a consumer Android application.
CorpBot.py is a production Discord bot implemented as a modular cog-based application on discord.py/py-cord. It provides a broad set of server tools: moderation (kick/ban/mute/lockdown/strikes), XP and role progression, music playback through Lavalink/pomice, games (Cards Against Humanity, Minesweeper, Mad Libs), message automation, web scrapers (Reddit, comics, PC part picker, hardware specs), utility commands (translation, encoding, weather, time), and an AIML-driven chat brain. Main.py bootstraps an AutoShardedBot, dispatches message and event hooks to every loaded cog, and provides an interactive console for reboot/update/shutdown; WatchDog.py supervises the process and restarts it based on exit codes. The architecture is organized around dozens of Cogs/ modules that follow a common setup(bot) pattern, pulling utility cogs such as Settings, Utils, DisplayName, Message, and PickList from the bot. Persistent state is stored as JSON through the Settings cog, which exposes server/user/global stat getters and setters; some branches support MongoDB and Redis. Commands are gated by owner/bot-admin/admin permission helpers, and background task loops are started and stopped via extension load/unload listeners. External dependencies include the Discord API, a Lavalink music server, and many public HTTP APIs, along with bundled AIML corpus files and JSON data files. Despite its breadth, the codebase shows organic growth: copy-pasted permission checks, deprecated discord.py API usage, fragile HTML scrapers, dead code paths, and at least one hardcoded credential are present. The most valuable reusable pieces are small cross-cutting utilities (async HTTP downloader, reaction-based pagination, fuzzy search, humanized time formatting) rather than the feature cogs themselves. This is overwhelmingly an application repo, though it ships a substantial conversational-AI knowledge base that could be treated as a data asset independent of the bot.
Pheweb is a full-stack web application for building interactive PheWAS (Phenome-Wide Association Study) websites from GWAS summary statistics. It provides a command-line pipeline to ingest association files, annotate variants with rsIDs and genes, compute Manhattan and QQ plots, and generate a searchable, browsable web interface with LocusZoom region views, phenotype correlations, and top hits tables. The architecture is a Flask monolith with a JavaScript frontend using D3.js, jQuery, and Bootstrap. While the codebase is well-organized for its domain and includes some reusable components (e.g., a simple flat-file indexer and a CFFI matrix builder), it suffers from significant technical drift: outdated dependencies (Flask 1.1, jQuery 1.12, Bootstrap 3.3.7, D3 v5), deprecated Python patterns, and a successor project (PheWeb2) explicitly recommended in the README. The project is functionally complete but in maintenance mode, with limited test coverage and several known bugs documented in the changelog.
nOS Client is an Electron-based desktop application that serves as a wallet and decentralized application (dApp) browser for the NEO blockchain. It provides a virtual operating system metaphor with a built-in webview-based browser, account management, portfolio tracking, token transfers, and GAS claiming. The app integrates with the NEO network via neon-js, supports hardware wallets (Ledger) and mnemonic-based key management, and exposes a custom JavaScript API (NOS.V1) to dApps through a request processor. The codebase is organized as a standard React/Redux SPA with multiple feature modules (auth, browser, account, settings, appstore) and heavy use of higher-order components for state management. The application is feature-rich but shows its age: dependencies are heavily outdated (Electron 2.x, Webpack 3, React 16.8 with recompose), and some sections like Exchange and Favorites are incomplete placeholders. Despite this, the core wallet and dApp browsing functionalities are implemented with reasonable modularity, though the reliance on legacy patterns and unmaintained libraries makes it risky to reuse without modernization.
This repository is a tutorial and research exploration of Graph RAG (Retrieval-Augmented Generation) combining vector databases (Weaviate) and knowledge graphs (RDF/SPARQL). It contains Jupyter notebooks that demonstrate building knowledge graphs from PubMed articles, World Bank documents, and Netflix movies, comparing vector search and structured query performance for retrieval-augmented generation. A Streamlit app provides an interactive demo for medical article search with MeSH term refinement and LLM summarization. The code is primarily educational, with reusable query modules for Weaviate, RDF, and Databricks, but lacks dependency pinning and has hardcoded credentials, limiting reproducibility. The repository is hybrid, with both application (Streamlit app) and data research (notebooks, datasets) elements, but the dominant character is data research as the core value lies in the experimental notebooks and data pipelines.
HelloGitHub is a curated monthly magazine that showcases interesting, beginner-friendly open-source projects from GitHub. The repository primarily consists of static Markdown files (over 250 issues in Chinese and English) organized by volume number, each following a consistent template with project descriptions, images, and sponsor sections. The only executable code is two Python scripts: one for generating new issues from a template (script/make_content/make_content.py) and one for monitoring GitHub star events and sending email summaries (script/github_bot/github_bot.py). The repository is not a software application in the traditional sense—it is a content publication project with minimal automation. The code quality is average; the scripts are simple and tightly coupled to the repository's directory structure, offering limited reusability. The value of the repo lies in its curated content, not its software craftsmanship.
This repository is a curated collection of front-end developer interview questions, organized by topic (General, HTML, CSS, JavaScript, Testing, Performance, Network, Coding, Fun) and translated into 30+ languages. It is built as a static website using the Eleventy (11ty) static site generator, with Nunjucks templates, Markdown content files, and a modest CSS/JS asset pipeline. The core value is entirely in the question content and its community translations; the application layer is a thin publishing wrapper. There are no reusable software components of note — the Eleventy config, CSS, and JS are all straightforward boilerplate for a documentation-style static site. The project's influence stems from its content curation and community adoption, not from any technical craftsmanship in the codebase.
This repository is primarily a large collection of GPT prompt templates (markdown files) designed for use with AI chat platforms like FlowGPT or gptcall.net. Each prompt file defines a specific role or task for the AI, such as a resume editor, coding tutor, fitness planner, or creative writing assistant. The repository also includes an Android application (OpenClaw and Codex) referenced in the README, along with Node.js scripts (update.mjs, db.mjs) for managing the prompt data. The prompts are structured with placeholders for user input and often request specific output formats, enabling users to import them into chat interfaces to obtain specialized AI behavior without crafting prompts from scratch. While the prompt library is extensive, it contains significant duplication, minimal-effort entries, and some policy-risking content (e.g., jailbreaks, NSFW role-play), which affects overall quality and reuse potential.
NSLogger is a remote logging framework for Apple (iOS, macOS, tvOS) and Android platforms. It consists of client libraries (C/Objective-C Swift wrapper for Apple, Java for Android) that send structured log messages (text, binary data, images) over TCP to a desktop viewer application. The desktop viewer (macOS app) provides real-time log viewing with filtering, color coding, search, marks, export, and preference management. An iPad viewer application also exists for on-device log viewing with Core Data persistence and Bluetooth support. The codebase includes multiple Xcode projects for different targets, test apps, and vendored third-party libraries (BWToolkit, HockeySDK-Mac, SSSelectableToolbar). While functional and well-known (4.9k stars), the project shows significant age: manual memory management (non-ARC), duplicated viewer logic across Desktop and iPad, incomplete features (JSON message format stubbed), outdated dependencies, and deprecated API usage. It remains a valuable reference for implementing a custom binary logging protocol and network transport layer, but would require modernization for current platform versions.
This is the official Scratch 3.0 graphical user interface (scratch-gui), a React/Redux single-page application that provides the complete web-based editor for creating, editing, and running Scratch projects. It integrates tightly with the Scratch ecosystem (scratch-vm, scratch-blocks, scratch-render, scratch-storage, etc.) to deliver block-based programming, sprite/costume/sound management, stage rendering, hardware extensions, cloud variables, tutorials, and project save/load. The architecture is heavily modular with many Higher-Order Components (HOCs) and relies on a centralized Redux store. While the codebase is large and well-structured for its domain, it exhibits significant technical drift due to outdated dependencies (React 16, Redux 3, Jest 21) and reliance on deprecated lifecycle methods. The repository is being archived and migrated to the scratch-editor mono-repo, as announced in the README.
This repository is a plugin ecosystem for Koolshare-modified Asuswrt-Merlin router firmware. It provides a software center (softcenter) that manages the installation, update, and removal of various router plugins, including DDNS (ddnspod, phddns, appledns), VPN (shadowvpn), download acceleration (kuainiao), network utilities (dualwan, swap, ssid), and a web-based terminal (shellinabox). The architecture is a collection of shell scripts and ASP web pages, with a central softcenter module that handles app store functionality, version checking, and offline installation. Key entry points include softcenter's install.sh, ks_app_install.sh, and Main_Soft_center.asp. Data flows involve downloading plugins as tar.gz archives from remote servers (koolshare.cn, GitHub raw), installing via scripts, and storing configuration in a dbus key-value store. External dependencies include precompiled binaries (curl, wget, perp, speedtest, shadowvpn, shellinaboxd) and remote endpoints for version checks and push messages. The codebase is heavily duplicated, with many identical backup.sh and install/uninstall scripts across modules, and relies on opaque UPX-packed binaries. Maintenance risks include hardcoded endpoints, outdated toolchains, and lack of tests or CI/CD.
This repository contains a proof-of-concept CLI tool for recovering text from pixelated screenshots, specifically targeting password recovery. The core algorithm identifies same-color rectangles in the pixelated image, computes their average color (with optional gamma correction), and matches them against a search image containing a De Bruijn sequence of expected characters. Geometric relationships between matched blocks are used to resolve ambiguous matches. The tool is implemented as a single Python script (depix.py) with a supporting library (depixlib) for image loading, rectangle detection, and matching logic. Additional utility scripts generate pixelated images and visualize detected boxes. The code is functional but lacks tests, dependency pinning, and modern packaging; it is a proof-of-concept rather than a production-ready application. The README indicates the project has migrated to Codeberg, suggesting the GitHub repository is no longer actively maintained.
This repository is a Chinese translation of the '500 Lines or Less' book (aosabook/500lines), containing twelve educational chapters each implementing a small, self-contained software system in roughly 500 lines of code. The chapters cover diverse topics including a dynamic build system (Contingent), a flow shop scheduler, optical character recognition, static analysis in Julia, an in-memory graph database (Dagoba), a key-value store (DBDB), a 3D modeller, an archaeology-inspired database, a web crawler with async coroutines, a distributed consensus system, a continuous integration system, and a simple web server. The code is intentionally simplified for teaching purposes and is accompanied by Chinese language articles. The repository is a collection of independent applications rather than a single coherent system, and while the code demonstrates clear patterns and architecture, it is largely educational and not production-ready. Many components rely on outdated language versions (Julia 0.3, Python 2.7, JavaScript ES5) and have minimal error handling, making extraction and reuse challenging without modernisation.
This repository is the open-source CLI client for Amazon Q Developer (formerly CodeWhisperer), now deprecated in favor of the closed-source Kiro CLI. It is a Rust workspace with approximately 2000 files, building two main binaries: `q` (terminal chat assistant) and `qchat` (legacy chat binary). The codebase is dominated by auto-generated AWS SDK client crates (amzn-codewhisperer-client, amzn-codewhisperer-streaming-client, amzn-qdeveloper-streaming-client, amzn-consolas-client, amzn-toolkit-telemetry-client), which are Smithy-generated and checked in. Hand-written code includes the chat CLI interactive loop, an agent framework with MCP (Model Context Protocol) support, a semantic search client using local ONNX models (MiniLM) and BM25 indexing, authentication (OIDC with device grant flow), telemetry, and an OS abstraction layer. The architecture is essentially a monolithic CLI application with multiple supporting libraries. About 90% of the source files are generated code, which means the hand-crafted components are relatively small. The project was previously actively maintained but is now effectively archived; the README states only critical security fixes will be accepted.
kyt is a deprecated monorepo CLI toolkit from The New York Times for scaffolding and developing JavaScript web applications. It encapsulates build tooling (Webpack 4, Babel 7), linting (ESLint 7), testing (Jest 27), and provides starter templates for React apps with client-only, server-only, or universal (isomorphic) rendering. The core package provides three primary commands: `kyt dev` (hot-reloading dev server), `kyt build` (production builds), and `kyt setup` (project scaffolding). Architecture: monorepo with Lerna + Yarn Workspaces; the CLI entry is `packages/kyt-core/src/index.js`; configuration is centralized in `kyt.config.js`, and runtime support (dynamic imports, SSR resolution) is provided by `packages/kyt-runtime`. The tool is no longer maintained and uses dependencies that are significantly behind modern versions (Webpack 4, React 17, Jest 27, ESLint 7). Its value lies in its clean composition of presets, configs, and custom ESLint rules that can be extracted and reused independently.
OpenUserJS.org is a Node.js/Express web application that serves as a hosting platform for user scripts (userscripts) and JavaScript libraries. It provides full CRUD operations for scripts, including upload, version management, GitHub import, and metadata parsing via PEG.js grammars. The platform includes community features such as user authentication (OAuth/OpenID via Passport.js), voting, flagging, moderation, discussions, issue tracking per script, and group management. The architecture follows a monolithic Express pattern with MongoDB (Mongoose) for persistence and AWS S3 for script storage. The frontend is server-rendered using Mustache templates with Bootstrap 3 and various client-side libraries (Ace editor, jQuery, highlight.js). The codebase demonstrates a comprehensive implementation of a community-driven script repository with rate limiting, security headers, and role-based access control (admin, moderator, user). Key modules include controllers for scripts, users, discussions, and moderation, along with utility libraries for model parsing, search, pagination, and async task orchestration. While the application is functional and has been in production for years, it exhibits significant technical debt: deprecated dependencies (request, underscore, moment), inconsistent error handling, hardcoded configuration, and a large number of TODO/FIXME comments. The code is not particularly modular or testable, and there are no automated tests visible in the repository. Despite these issues, the repository contains several well-crafted components that could be extracted and reused in other Node.js projects, such as the PEG.js grammar for userscript metadata parsing and the async task helper library. The overall quality is average, with room for improvement in modernisation, testing, and code organisation.