nccgroup / nccgroup/singularity

Private Network Access update

Open
#56 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.3k
Forks
161
PR merge metrics
No merged PRs in 30d

Description

0.0.0.0 bypass is not available after Chrome version 129.

Feature: Deprecate 0.0.0.0 for Private Network Access

Private Network Access will add web workers in Chrome 130 130+.

Private Network Access: Extended protection for web workers and navigation fetches

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No files, tests, or entry points are named. Start by reading the linked Chrome Status and developer.chrome.com updates, then locate the JavaScript handling for the 0.0.0.0 bypass and Private Network Access behavior. Done should mean the framework's intended behavior is defined and works with Chrome 130+.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
networking, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.