unstale

npm / @metamask/phishing-warning

@metamask/phishing-warning

What changed in @metamask/phishing-warning 2 to 6, from its official release notes, upgrade guides and advisories. Sources checked 2026-11-05.

8 breaking2 behavior and defaults5 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.11 on npm

@metamask/phishing-warning 64 changes

Breaking changes 1

  • The minimum Node version is now 22, with support for Node 22, 24, and 26+.

    6.0.0release notes

Behavior and default changes 1

Fixes and other changes 2

  • The phishing warning page favicon now matches the new MetaMask brand.

    6.0.0release notes

  • The phishing warning page's X sharing link now uses the current MetaMask domain.

    6.0.0release notes

@metamask/phishing-warning 54 changes

Breaking changes 2

  • The data: protocol is now disallowed alongside javascript:.

    5.0.0release notes

  • The vbscript: protocol is now disallowed alongside javascript:.

    5.0.0release notes

Fixes and other changes 2

@metamask/phishing-warning 41 changes

Breaking changes 1

  • phishingSafelistStream now sends origin instead of hostname as a parameter to safelistPhishingDomain.

    4.0.0release notes

@metamask/phishing-warning 32 changes

Breaking changes 2

  • The minimum supported Node.js version is now 16.

    3.0.0release notes

  • This package now returns streams conforming to the API of readable-stream@3.x.

    3.0.0release notes

@metamask/phishing-warning 24 changes

Breaking changes 2

  • The query parameter is no longer accepted; the page looks up the source of a block dynamically instead.

    2.0.0release notes

  • The page no longer shows which project is responsible for the block; this will return in a future version.

    2.0.0release notes

Behavior and default changes 1

  • The page now looks up the source of a block dynamically.

    2.0.0release notes

Fixes and other changes 1