uwiger/gproc

Gproc is a distributed process registry for Erlang that provides global and local registration, property tracking, and aggregated counters. It extends standard process management with publish/subscribe messaging, monitoring, and load-balancing pool capabilities, all supported by comprehensive automated testing.

A new header file, include/gproc.hrl, was added to the project. This file contains the Apache 2.0 license header and defines the macro ?TAB as gproc, which is used for specifying attributes at registration time.

include · high confidence

Added a .gitignore file to exclude build artifacts and temporary files, an Emakefile for Erlang compilation, a Makefile with targets for compilation, testing, and documentation, and a LICENSE file specifying the Apache 2.0 license. Additionally, rebar.config and rebar.config.script were added to manage dependencies (including conditional fetching of gen\_leader and edown) and build profiles, while zompify.sh and related metadata files were introduced to support the zomp packaging tool.

(repo-wide) · high confidence

Gproc has been restructured into a full-featured distributed process registry. The \gproc\ module now supports global and local registration, shared properties, and aggregated counters. A new \gproc\_dist\ module handles distributed synchronization and leader election. The library adds a publish/subscribe system (\gproc\_ps\), a notification system (\gproc\_monitor\), and a load-balancing pool manager (\gproc\_pool\). The application structure has been updated to include these new components, and the license has been changed to Apache 2.0.

src · high confidence

The \patches\ directory has been cleaned of obsolete Erlang standard library modules, specifically removing \gen\_leader\, \application\_master\, \gen\, \gen\_event\, \gen\_fsm\, \gen\_server\, \supervisor\, and \sys\. These files, which implemented generic server behaviors and application management, have been deleted, indicating a shift away from these legacy implementations.

patches · high confidence

Added three new files in the priv directory to handle dynamic dependency resolution during the build process. The check\_edown.script and remove\_deps.script files enable the build system to conditionally include or exclude the edown dependency based on whether documentation is being built, ensuring the build does not fail if edown is not present. Additionally, an empty sys.config file was added to the priv directory.

priv · medium confidence

The documentation in the \doc\ directory has been converted from HTML to Markdown format, with new \.md\ files generated for each module (e.g., \gproc.md\, \gproc\_dist.md\) and a new \README.md\ for the project overview. The build process now uses \edown\ to generate GitHub-flavored Markdown, replacing the previous HTML-based documentation structure.

doc · high confidence

The gproc application's metadata has been updated to version 1.3.0, which includes a broader set of modules in the application definition. This change ensures that the application correctly registers and manages the expanded set of components, including test and utility modules, aligning the application structure with the current codebase.

ebin · medium confidence

Added QuickCheck model tests for gproc; Added distributed and remote testing infrastructure for gproc.

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

• CAI 60 → 58 (-1.9)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 89 → 90 (+0.8)
• Architecture 100 → 100 (+0.0)
• Maturity 53 → 56 (+3.0)
• Readiness 57 → 50 (-7.0)
• Security 61 → 60 (-1.4)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• No exposed public API
• Off-boarding risk: anonymized user #1
• Test reliability not included
• The 'Use case: Environment handling' section is cut by the scanner and the full module outline exists. (README.md)
• The 'Use case: Pub/Sub patterns' section is cut by the scanner and the full module outline exists. (README.md)
• The 'Use case: System inspection' section is cut off by the scanner before describing Pub/Sub patterns, Environment handling, and Testing. (README.md)
• TooManyMethods: gproc (src/gproc.erl)
• TooManyMethods: gproc_dist (src/gproc_dist.erl)
• TooManyMethods: gproc_lib (src/gproc_lib.erl)
• TooManyMethods: gproc_pool (src/gproc_pool.erl)
• Behaviours: application - again, the referenced application documentation is not linked to this module's README. (doc/gproc_app.md)
• Behaviours: gen_server - the referenced gen_server documentation is not linked to this module's README. (doc/gproc_bcast.md)
• complexity unreadable for .erl, .hrl — churn × complexity hotspots could not be measured

• Coverage not measured — no coverage collector is wired up
• Dependency hygiene PARTLY measured — rebar3 pinning read, dependency currency not (no rebar.lock-pinned Hex declaration to grade)
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• Duplicated block (10 lines × 2) (src/gproc.erl)
• Duplicated block (6 lines × 2) (src/gproc.erl)
• Duplicated block (6 lines × 2) (src/gproc_dist.erl)
• Duplicated block (7 lines × 2) (src/gproc_dist.erl)
• Floating source dependency: gen_leader
• High: security finding (details withheld)
• Medium: security finding (details withheld)
• No dependency lockfile committed (rebar.config)
• Off-boarding risk: anonymized user #1
• TodoComment (eqc/gproc_eqc_tests.erl)
• TodoComment (eqc/gproc_eqc_tests.erl)
• gproc.handle_call (cognitive 42) (src/gproc.erl)
• gproc.handle_call (cyclomatic 72) (src/gproc.erl)
• gproc.process_is_down (cognitive 18) (src/gproc.erl)
• gproc.process_is_down (cyclomatic 16) (src/gproc.erl)
• gproc.try_alternative (cyclomatic 21) (src/gproc.erl)
• …and 6 more

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

uwiger/gproc 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.