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

Add edgekit, a shared guard for the HTTP edge

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
backend, security

Research direction

The payload names no files or tests in this repository. Start with the gouncer proxy-list package it mentions and the standard library's cross-origin protection, which the proposal says to wrap. Settle the module's API for client address, scheme and host, the public address option, refusal logging, report-only mode and the dialer's address checks before writing code. Done means a new edgekit module on the standard library with tests for trusted-proxy resolution and refusals, agreed with the maintainers first.

Written by the indexing model from the issue text.

Description

enhancement

Downstream applications need one shared guard for writes from other sites, forwarded headers and outbound calls.

Current state: one application carries its own cross-origin guard and forwarded header rules. Any other application would have to copy them. Each reads the proxy list through gouncer but parses its public address itself.

Proposal: a new edgekit module on the standard library only. It works out the client address, scheme and host once, from trusted proxies only. It wraps the standard cross-origin protection with an optional public address. It logs a reason for each refused write. It offers a report-only mode and lets the application write the refusal. A dialer refuses loopback, private and link-local addresses.

Trigger: a second application needs the guard.

Dominant language
Go
Stars
69
Forks
3
Avg merge
9h 11m
Merged PRs (30d)
38

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 gopherium/framework

All issues in gopherium/framework

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.