-
Notifications
You must be signed in to change notification settings - Fork 774
Add MITY #1185
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.
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
base: master
Are you sure you want to change the base?
Add MITY #1185
Conversation
Wiz Scan Summary
To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension. |
hey @wbnns, hope you are doing good! any news on that pr? |
Hi @scagria can you rebase against master? Your PR is failing CICD but I just merged a fix that might help. |
hey @fainashalts, can you check now? |
Hello, how long does it take normally to be review? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Financial
More Details
Attribute | Value |
---|---|
Data Classifier | Financial/Ethereum Address |
Data Classifier ID | BUILTIN-388 |
Sampled Examples
Key | Value |
---|---|
ethereum.address | 0x*eA...**13 (42 chars) |
Rule ID: BUILTIN-388
To ignore this finding as an exception, reply to this conversation with #wiz_ignore reason
If you'd like to ignore this finding in all future scans, add an exception in the .wiz file (learn more) or create an Ignore Rule (learn more).
@fainashalts can you help me understand why its failing? pr is following the rules and this isn’t the first token integration pr we have created - it follows the same pattern. so why is this one failing the check? the l1 token name and l2 token names are different, so i made a change in the json file assuming that might be the issue but it is still failing. it would be great if i can get a response, as this is delaying our launch. thank you! |
Hi @scagria I'm looking into it, will try to get this sorted out asap! |
thank you! |
Hi @scagria thank you for your patience! I took a close look at this PR and it looks like the issue is that the name on Ethereum is different from what you have in the json. We can add a per-chain override to fix this, like so:
I added a suggested commit to fix this. Please let me know if you have any questions! |
Co-authored-by: Faina Shalts <[email protected]>
@fainashalts done, thank you for the help! |
Adding Fission Bio (MITY)
Ethereum: https://etherscan.io/token/0xd07ea8776e52c1b67dca6ffbc3f659fc9fbe4113
Base: https://basescan.org/token/0x1fbaf8bdc2a43b0c9ba90b6caf44ee14d2ee6773