Search Results for "core-analyzer"

...The repo provides automated, periodic releases (e.g. weekly or on schedule) and also offers a CLI tool so users can regenerate or customize geo data in the format they need — for example, producing a .dat file for V2Ray / Xray-core, or a MaxMind-compatible .mmdb.

Fuite is a command-line tool for detecting JavaScript memory leaks in web applications through automated Chrome testing. It launches Chromium with Puppeteer and repeatedly runs user interactions to identify objects that accumulate across iterations. The analyzer checks heap objects, event listeners, DOM nodes, arrays, maps, sets, and plain objects. Its default scenario navigates internal links and returns to the starting page, which works well for client-rendered applications. Custom scenarios can model dialogs, authentication, navigation, or other application-specific interactions. Results can be written to JSON, and optional heap snapshots support deeper analysis in Chrome DevTools. ...

...It focuses on replacing repeated manual prompting with systems that prompt, verify, schedule, and hand off work over time. The project is aimed at developers using tools such as Grok, Claude Code, Codex, Cursor, and other coding agents. It explains core building blocks such as scheduling, worktrees, skills, plugins, connectors, sub-agents, and persistent memory or state. The repository includes production loop patterns, quickstarts, starters, checklists, safety notes, and real-world stories. It also provides CLI tools such as loop-audit, loop-init, and loop-cost to scaffold, evaluate, and estimate agent loop workflows.

The M6811 Code-Seeking Disassembler is a command-line tool that lets you enter known starting vectors for a given code image for the 6811 micro. It will disassemble the code and follow through branches to assist in the separation of code and data. Its companion Fuzzy Function Analyzer uses DNA Sequence Alignment Algorithms to locate similar code in multiple binaries, facilitating reverse-engineering. Originally written to analyze code from GM automotive engine controllers, but is useful anywhere a 6811 micro is being used. Version 1.0 was written in Borland Pascal in April 1996, and updated to v1.2 in June 1999. ...