uwiger/setup

This system is a generic Erlang utility application designed for initializing and configuring Erlang-based systems. It provides a framework for bootstrapping environments through configurable hooks, variable expansion, and the generation of escript-based boot scripts. The tool supports reading configuration from archives and integrates with standard Erlang build tools like rebar3 and the xtest framework for validation.

A new example configuration file (gproc.conf) has been added to the examples directory. This file configures the Erlang runtime to start the kernel, stdlib, sasl, and gproc applications, providing a ready-to-use setup for users testing the gproc library.

examples · high confidence

New Erlang application source files (testapp.app.src, testapp\_app.erl, testapp\_sup.erl) were added to the xtest/testapp-1 and xtest/testapp-2 directories. These files define the application structure, supervision tree, and start/stop callbacks, enabling the test applications to be built and managed by rebar.

xtest/testapp-1, xtest/testapp-2 · high confidence

This entry marks the initial commit of the Setup application, a generic utility for initializing and configuring Erlang-based systems. The release introduces a new Makefile for build automation, a .gitignore file, and an Apache 2.0 LICENSE. It adds rebar3 compatibility via a rebar.config.script and rebar.lock, and configures the build to generate an escript named setup\_gen as a post-compile hook. The project also includes updated documentation (README.md) and initial test infrastructure.

(repo-wide) · high confidence

This change introduces the complete documentation set for the \setup\ Erlang application, including the main README, module reference pages for \setup\, \setup\_file\, \setup\_gen\, and \setup\_lib\, and supporting assets like the EDoc configuration and CSS stylesheet. The documentation details the \setup\_gen\ utility for generating boot scripts and releases, the \setup\ application's framework for initializing systems via hooks, and its support for variable expansion in application environments. It also covers the \setup\_file\ module's ability to read configuration files from zip and escript archives, and the \setup\_lib\ utility functions.

doc · high confidence

Added a suite of new configuration files (test.conf, test\_1.conf through test\_4.conf) that define test environments, application dependencies, and variable passing mechanisms for the xtest framework. Additionally, symbolic links to the rebar build tool were added in the testapp-1 and testapp-2 directories to support rebar3 builds.

xtest · high confidence

The setup application's entry point has been refactored from a direct process-based start to a standard OTP supervisor structure. The \setup\_app\ module now implements the \application\ behavior, starting the \setup\_sup\ supervisor which manages the \setup\_srv\ gen\_server. The actual setup logic is triggered via a \run\_setup\ start phase, controlled by the \auto\_run\_phases\ environment variable. This change replaces the previous monolithic start function with a more robust, structured lifecycle management for the setup process.

src · high confidence

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

• CAI 52 → 61 (+8.8)
• Rubric changed (rubric-2026.09.12 → rubric-2026.09.18) — scores are not directly comparable.

• Code Health 91 → 91 (+0.0)
• Architecture 100 → 100 (+0.0)
• Maturity 45 → 48 (+2.8)
• Readiness 43 → 65 (+22.0)
• Security 60 → 70 (+10.0)

• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• No automated tests
• No tests found
• Test reliability not included

• Dependency hygiene PARTLY measured — rebar3 pinning read, dependency currency not (no rebar.lock-pinned Hex declaration to grade)
• Documentation: no project overview (README.md)
• No ADRs found

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

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