Crabpot is a compatibility testing and regression detection framework for the OpenClaw AI agent plugin ecosystem. It validates plugin fixtures (59 plugins, 119 entrypoints) against the OpenClaw API surface by capturing contract registrations, running synthetic probes, measuring cold-import readiness, and profiling resource usage. The system is driven by a modular collection of Node.js scripts (ES modules) that orchestrate inspection, report generation, and CI policy enforcement. It integrates deeply with GitHub Actions for automated checks, track dashboards, and resource campaign execution via Docker. The architecture is script-based rather than a monolithic application, with each script performing a focused task (e.g., capture-contracts.mjs, synthetic-probes.mjs, generate-report.mjs) and producing JSON+Markdown reports. External dependencies include the OpenClaw plugin-inspector library, npm/git for fixture materialization, and GitHub Actions for CI. The framework is designed to catch contract drift before external plugin authors encounter it, and it maintains a dashboard of live issues, compat gaps, and profile regressions.
This repository is a curated markdown list of companies that use non-whiteboard interview techniques. Despite having 50K+ stars, it is not a software application in any meaningful sense — it is a community-maintained README with a CI pipeline that validates markdown formatting and link integrity. The only source file, index.js, is an empty module export (effectively a no-op). All 'functionality' lives in the CI workflow and package.json linting configuration. The architecture is trivial: GitHub Actions runs two jobs on PRs/pushes to main. The 'remark' job installs Node dependencies and runs remark-cli with a set of linting plugins to enforce markdown style (alphabetized lists, no tabs, no trailing slashes on URLs, etc.). The 'links' job uses lychee-action to verify all URLs in README.md return valid HTTPS responses. There is no application logic, no data processing, no API — just static file validation. The repository's value is entirely in the README content (the company list), not in any code. The CI pipeline is a standard, unremarkable markdown linting setup. The last commit was in June 2026, but the project has no real development trajectory — it accepts PRs that add list entries and runs CI to validate them. The codebase itself has no reusable components; the CI workflow is generic boilerplate that could be copied from any markdown linting tutorial.