Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Make the anonymous-operator audit gate config-driven: add `compliance.allow_anonymous_operator` beside `FORGELM_ALLOW_ANONYMOUS_OPERATOR`

Open
  • Is something wrong?
#913 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
security

Research direction

Start with the environment check in AuditLogger.__init__, then the same FORGELM_ALLOW_ANONYMOUS_OPERATOR reads in doctor and approve. Do not start until #706 is settled, since it may close this row instead. If the field is added, thread compliance.allow_anonymous_operator through those call sites with YAML taking precedence, and cover the precedence in a test. Done means the field is documented in EN and TR, the template is updated, and the row is removed from docs/roadmap/risks-and-decisions.md with its ID named in the CHANGELOG.

Written by the indexing model from the issue text.

Description

area: config severity: low source: roadmap wave: 4

Deferred work · F-PR29-A6-14 · severity Low · cost ~30 min (more in practice) · recorded in docs/roadmap/risks-and-decisions.md:87

Summary

Whether the audit logger refuses to start when no operator identity resolves is decided only by the FORGELM_ALLOW_ANONYMOUS_OPERATOR=1 environment variable (read in AuditLogger.__init__, and again in doctor and approve). The config-driven principle keeps behaviour gates in validated YAML and environment variables for secrets. The PR #29 plan adds compliance.allow_anonymous_operator: bool = False, with YAML taking precedence and the variable kept as a CI fallback.

Condition or budget

None recorded. Settle #706 first: it proposes the opposite fix (documenting identity variables as permitted), which would make this row moot.

State today (re-checked 2026-10-09)

No allow_anonymous_operator field exists; AuditLogger takes no config, so the field has to be threaded through its call sites.

Related

#706 (CR-A13-063) — the competing fix; #714 (CR-A04-086) asks for one shared operator-identity helper.

Acceptance criteria

  • Either the field exists (description, template entry, EN/TR docs, precedence tested) or #706's position is adopted and this row is closed with that reason.
  • The row is removed from the deferral table and the CHANGELOG names its ID (the table's removal contract).

Recorded in docs/roadmap/risks-and-decisions.md (read at f94595f) and re-checked against the code on 2026-10-09. The row leaves that table only when the fix is on main, the CHANGELOG names its ID and any promised guard exists.

Dominant language
Python
Stars
9
Forks
1
Avg merge
8h 10m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from HodeTech/ForgeLM

All issues in HodeTech/ForgeLM

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.