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

Seam request: EgressClassGuard: make the inference-tool match configurable

Open Beginner friendly
#2,349 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 11 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
security, tooling

Research direction

Start with hooks/EgressClassGuard.hook.ts:104, where the two literal filenames are gated, and inspect how this project loads configuration. Add a configurable name or pattern list with the current filenames as the default, then verify renamed, wrapped, and additional Tier-2 tools are covered. Done means the active patterns are logged once at load and matching no longer depends solely on OpenRouter.ts or Cerberus.ts.

Written by the indexing model from the issue text.

Description

Problem. hooks/EgressClassGuard.hook.ts:104 gates only commands that match the literal filenames OpenRouter.ts or Cerberus.ts. If an install renames or wraps the tool (to add a proxy, for example), the guard stops covering it with no signal. If it adds a second Tier-2 inference tool, that tool is never covered.

Proposed change. Read the list of gated tool names or patterns from config (canon default: the current two), for example [egress.tier2_tools]. Log once at load which patterns are active.

Why canon benefits. The egress guard keeps covering the real inference path after any rename or addition, so it fails closed, not silently open.

Dominant language
TypeScript
Stars
19.4k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 danielmiessler/LifeOS

All issues in danielmiessler/LifeOS

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.