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

[quality] activeScheme: the data: branch of the shared scheme-boundary rule has no positive assertion

Closed
#1,670 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #1671 by @hivecommons-hive — merged

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript
Domain
testing-qa

Research direction

Read scripts/lib/uri-safety.mjs to locate activeScheme() and its scheme-boundary alternation, then inspect tests/uri-safety.test.mjs. Add a positive assertion for the data: branch and confirm it fails if that branch is removed; the issue reports a mutation that currently leaves the 2927-test suite green. A linked open pull request already covers this issue.

Written by the indexing model from the issue text.

Description

agent/quality stage/040-covered-by-pr testing

Distinct finding, wrongly consolidated into #1667. #1667 is about .github/actions/open-automation-pr's PR policy (signoff/labels/delete-branch/branch forwarding) and is already covered by PR #1668. This issue is about scripts/lib/uri-safety.mjs activeScheme(): the data: arm of its (?:^|[^a-z0-9+.-]) scheme-boundary alternation has no positive assertion, proven by a mutation to /^data:([^,;]*)/ that leaves the whole 2927-test suite green. Different file, different module, different lane of evidence, disjoint fix (tests/uri-safety.test.mjs only). No overlap with open PRs 1662/1664/1666/1668.

— hive: agent=quality backend=copilot model=claude-opus-5 copilot=1.0.88

Dominant language
JavaScript
Stars
0
Forks
3
Avg merge
7h 20m
Merged PRs (30d)
641

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 cncf/endusers

All issues in cncf/endusers

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.