Git Config module

[bpmct]

A discussion dedicated to the Git Config module. Share your thoughts, questions, and feedback here.

Module Scorecard

Presentation & Onboarding	Credential Hygiene	Restricted-Environment Readiness	Engineering Quality	Overall
12 / 17	20 / 20	2 / 2	7 / 10	84 / 100

Drilldown

Presentation & Onboarding — 12 / 17

Criterion	Max	Score	Notes
Configuration-mode examples	12	12	README documents three examples covering the major modes: default usage, allow_email_change = true, and both allow_username_change = false / allow_email_change = false. The two primary boolean toggles are each demonstrated with sensible defaults.
Visual preview	5	0	README contains two "TODO: Add screenshot" placeholders. No image, GIF, or video is embedded.

Credential Hygiene — 20 / 20

Criterion	Max	Score	Notes
Secrets marked sensitive	16	16	The module has no sensitive inputs (only agent_id, two booleans, and a number). No sensitive = true is needed. README examples contain no inline secrets or placeholder keys.
Non-hardcoded auth path	4	4	Identity is sourced from data.coder_workspace_owner.me (Coder's native workspace-owner data source). No raw API keys, tokens, or hardcoded credentials are required.

Restricted-Environment Readiness — 2 / 2

Criterion	Max	Score	Notes
Mirrorable artifact source	5	N/A	Module downloads or installs nothing; it only invokes git config already present in the image.
Bring-your-own binary	10	N/A	No binary is downloaded or installed by the module.
Egress transparency	3	N/A	Module contacts no external endpoints; it runs a local git config script.
Runs without sudo	2	2	The coder_script runs git config --global user.name … and git config --global user.email … with no sudo invocation. Writes to ~/.gitconfig as the unprivileged user.

Engineering Quality — 7 / 10

Criterion	Max	Score	Notes
Input quality	6	3	All four variables have clear description fields and sensible defaults (allow_username_change = true, allow_email_change = false, coder_parameter_order = null). However, no validation blocks are present on any input (e.g., agent_id could enforce non-empty, coder_parameter_order could enforce a positive integer).
Test coverage	4	4	main.test.ts provides a clear testing story: testRequiredVariables plus five runTerraformApply cases covering disabled/enabled overrides, empty-email edge case, and parameter ordering. Tests verify resource counts, types, names, and order attributes—directly exercising the module's business logic.

Overall — 84 / 100

Raw 41 / 49 → round(41 / 49 × 100) = 84

Track: Utility (git configuration helper; not an AI agent or IDE). Restricted-Environment download criteria (Mirrorable, BYO binary, Egress) excluded as N/A; denominator reduced from 67 to 49.

---

Scored against SCORECARD.md on 2026-10-26 with solstice-1.