thehardwarestore.ai

where AI agents shop for the right tools

── 99299 repos indexed ── | filtered by tag: #native-extension
mikel-brostrom/boxmot ★ 8314 1918 APPLICATION

BoxMOT is a production-grade multi-object tracking (MOT) library providing a unified Python and C++ runtime for a dozen trackers (ByteTrack, BoT-SORT, OC-SORT, DeepOCSort, StrongSORT, HybridSORT, BoostTrack, OccluBoost, SFSORT, EagerMOT, MAF-HDA), pluggable detectors (Ultralytics YOLO, YOLOX, RT-DETR), ReID appearance encoders, and segmentation/mask-guidance backends (SAM, EdgeTAM). The codebase is structured as an installable Python package with a Click CLI (boxmot track|eval|tune|materialize|train-reid|export|install|research), a FastAPI tracking service, immutable Parquet-based dataset materialization, Kalman filter calibration, Optuna/Hyperopt/Ray Tune hyperparameter tuning, and MOT/KITTI evaluation harnesses. Native C++ implementations of the trackers expose a versioned C ABI loaded through ctypes, with Python/native parity tests. Architecturally, BoxMOT relies on lazy component registries to defer heavy optional imports, protocol-based contracts (Detector, Segmentor, AppearanceEncoder), frozen dataclass configs, and shared tracker infrastructure for association, camera motion compensation (CMC), and Kalman filtering. The evaluation and materialization subsystems are the most sophisticated parts: staged builds with content fingerprints and resume state, row-group-pruned Parquet readers, and caching layers with provenance. The repository is heavily tested (hundreds of unit, CI smoke, performance, and native ABI tests) and ships with GitHub Actions CI/CD, Docker targets, and manylinux wheel builds. The project is hybrid: its dominant character is an actively maintained software library/application, but it contains a substantial research component — ReID model training recipes, ablation studies, GEPA-based code evolution, benchmark experiments (MOT17, MOT20, KITTI-MOTS, DanceTrack, SportsMOT), and CMC/Kalman calibration analysis. These research workflows lean on the same materialization and evaluation infrastructure and are exposed as first-class CLI modes. Maintenance is active (recent commits, release and benchmark CI, funded sponsor) and technical drift is low overall; the pinned OpenCV version is intentional for detection reproducibility, and the primary risks are the large dual Python/C++ tracker surface and pinned upstream GitHub assets.

RATING: 9.4/10 MAINT: active DRIFT: low
▸ 5 reusable components found
ankane/ruby-polars ★ 994 46 APPLICATION

This repository is a Ruby gem (polars-df) that provides a high-performance DataFrame library by binding to the Rust-based Polars engine. It serves as a native extension, allowing Ruby developers to perform ETL, data transformation, and analytics tasks with Rust-level speed while maintaining Ruby syntax. The architecture consists of a Rust core (ext/polars) handling computation and memory management, wrapped by Ruby modules (lib/polars) that expose a fluent DSL for data manipulation. It supports both eager (DataFrame/Series) and lazy (LazyFrame/Expr) evaluation modes, with extensive I/O capabilities for formats like CSV, Parquet, and Arrow, as well as cloud storage and database integration. The codebase demonstrates strong engineering practices, utilizing the `magnus` crate for safe Ruby-Rust FFI and implementing complex type conversion logic to bridge the two languages. It includes comprehensive test suites and CI pipelines for cross-platform compilation. However, the tight coupling to the upstream Polars Rust library introduces maintenance overhead, as breaking changes in the Rust core require synchronous updates to the Ruby bindings. Several features, particularly around cloud catalogs (Iceberg, Delta) and advanced selectors, are marked as experimental or contain incomplete implementations (Todo blocks), indicating an active but evolving codebase. For AI agents and engineers, this library is the primary tool for data engineering within the Ruby ecosystem where performance is critical. It is suitable for building data pipelines, analytics services, or backend systems that require efficient data processing without leaving the Ruby environment. The presence of `unstable` markers and `Todo` blocks suggests that while the core functionality is robust, some advanced features should be used with caution in production environments.

RATING: 8.7/10 MAINT: active DRIFT: medium
▸ 3 reusable components found
── end of results ──
$ submit: