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

[aep] Build egress host accepts URL, path, and port forms at package resolution

Open Beginner friendly
#491 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start in packages/config-schema/src/agent-environment.ts:265-272 and packages/config-schema/src/agent.ts:49-56, where host strings are accepted. Add exact-host validation to the shared schema and extend the schema tests with URL, path, and embedded-port cases. Done means resolution rejects non-exact hosts and new tests pass.

Written by the indexing model from the issue text.

Description

bug doc-audit

Found by the independent documentation audit (agent-supply group, base b648f86).

Spec clause. Agent Environment Package, invalid package list: a build definition that "lacks an explicit exact {host, port} build egress grant" fails before effects.

Observed. packages/config-schema/src/agent-environment.ts:265-272@b648f86 and packages/config-schema/src/agent.ts:49-56 accept any non-empty host string without *, so https://x/y or a:443 passes resolution and reaches the AEP. NanoHost validates the grant only later, at build time (apps/nanohost/src/image_acquisition.rs:1885).

Required. Resolution refuses a host that is not an exact host name or address.

Adjudication. The code differs from a current accepted specification.

Repair direction. Validate the host form in the shared schema and add the URL, path, and embedded-port cases to the schema tests.

Severity hint. Low.

Dominant language
TypeScript
Stars
0
Forks
1
Avg merge
3h 54m
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 lingkaix/openkit

All issues in lingkaix/openkit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.