Releases: MetaMask/phishing-warning
Releases · MetaMask/phishing-warning
4.1.0
Added
- Redesign UI of the phishing warning page (#176)
4.0.0
Changed
- BREAKING: Update
phishingSafelistStream
to send origin
instead of hostname
as a parameter for safelistPhishingDomain
method (#165)
3.0.4
Changed
- Update index.html - update attribution copy (#161)
- chore(devdeps): @lavamoat/allow-scripts@^2.3.1->^3.0.4 (#157)
- Enabling MetaMask security code scanner (#151)
- remove globalthis polyfill (#149)
- Bump @metamask/post-message-stream from 7.0.0 to 8.0.0 (#146)
3.0.3
Changed
- Update
ses
to v1.1.0
(#143)
3.0.2
Fixed
- change to hostname for Github issues (#127)
3.0.1
Changed
- Using href url param only for suspect site (#124)
3.0.0
Changed
- BREAKING: Increase minimum Node.js version to 16 (#107)
- BREAKING: This package now returns streams conforming to the API of [email protected]. (#122) (#104)
- Bump @metamask/post-message-stream from ^6.2.0 to ^7.0.0 (#104)
- Upgrade obj-multiplex to @metamask/object-multiplex@^2.0.0 (#122)
Fixed
- Bump ses from ^0.18.7 to ^0.18.8 (#120)
2.1.0
Changed
- "Back to safety" button now triggers a
backToSafetyPhishingWarning
message to be sent on the phishingSafelistStream
(#84)
2.0.1
Fixed
- Restore iframe warning and "open in new tab" link (#73)
2.0.0
Changed
- BREAKING: Dynamically lookup the source of a block (#57)
- The query parameter
newIssueUrl
is no longer accepted. Instead this page will look up the source of a block dynamically.
- We no longer show on the page which project is responsible for the block. This will be restored in a future version.
- Redesign the phishing warning page (#52)