Skip to content

Add wolfxy.com to whitelist #1790

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
react-universe wants to merge 1 commit into
base: master
Choose a base branch
from
+2 −1
Open

Add wolfxy.com to whitelist #1790

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion whitelist.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,4 +30,5 @@
- url: "*.tistory.com"
- url: "*.surge.sh"
- url: revoke.cash
- url: nftplus.io
- url: nftplus.io
- url: wolfxy.com
Copy link

@coderabbitai coderabbitai bot Mar 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Whitelist-only addition likely won’t clear the reported warning.

Line 34 adds wolfxy.com to whitelist.yaml, but based on README.md (Line 19-35) whitelist/fuzzylist are not currently active, and build.js (Line 1-25) has no whitelist-over-blocklist conflict handling. This PR likely won’t satisfy the stated objective unless the active detection source is also updated.

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@whitelist.yaml` at line 34, The PR adds wolfxy.com to whitelist.yaml but
whitelist/fuzzylist are not enabled (per README) and build.js lacks
whitelist-vs-blocklist conflict handling, so the warning won't be cleared;
update the active detection source and conflict resolution: enable
whitelist/fuzzylist usage as described in README or change the detector to
consult whitelist.yaml/fuzzylist during runtime, and modify build.js to
implement logic that checks whitelist entries (exact and fuzzy) before applying
blocklist rules so whitelisted domains like wolfxy.com are exempt from blocking.