coregx/signals

This system is a reactive state management library for Go 1.25+ that provides type-safe primitives for managing state, derived values, and side effects. It enables automatic dependency tracking and lazy evaluation while ensuring thread safety and zero allocations in critical paths. The project includes a demonstration application to illustrate these core capabilities.

The \cmd/example\ package now includes a demonstration application that showcases the usage of the \github.com/coregx/signals\ library. This example illustrates core reactive state management features, including basic signal creation and updates, computed signals with single or multiple dependencies, and effects that run automatically on state changes, including cleanup logic and side-effect handling.

cmd · high confidence

This entry introduces the Signals library, a type-safe, reactive state management tool for Go 1.25+ inspired by Angular Signals. The release establishes the project's core reactive primitives: Signal\[T\] for reactive state, Computed\[T\] for derived state with lazy evaluation and caching, and Effect for side effects with automatic dependency tracking and cleanup. The library is designed for production use with thread-safe concurrent access, panic recovery in user callbacks, and zero allocations in hot paths. This initial commit also sets up the essential project infrastructure, including a comprehensive golangci-lint configuration for code quality, a Makefile and Taskfile for build and test automation, and standard repository documentation such as the README, CHANGELOG, and contributing guidelines.

(repo-wide) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 69 → 70 (+1.3)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 98 → 98 (+0.1)
• Architecture 69 → 69 (+0.0)
• Maturity 62 → 60 (-1.8)
• Readiness 68 → 84 (+15.6)
• Security 100 → 97 (-3.1)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• Duplicated block (10 lines × 2) (effect.go)
• Duplicated block (16 lines × 2) (computed.go)
• No exposed public API
• Test reliability not included
• early-stage repository — too little history to judge knowledge freshness
• git history depth insufficient
• git history depth insufficient
• single-maintainer — knowledge-concentration (bus factor) risk

• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• Duplicated block (10 lines × 2) (effect.go)
• Duplicated block (11 lines × 2) (computed.go)
• Duplicated block (11 lines × 2) (effect.go)
• Duplicated block (25–30 lines × 2) (computed.go)
• Duplicated block (9 lines × 7) (computed.go)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• No dependency advisory monitoring
• …and 1 more

• 1 commits — 1 feature/other, 0 fixes

• (root) — 1 commit

• change: feat: add starhistory.io star chart to README (#8)

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

coregx/signals was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.