-
Notifications
You must be signed in to change notification settings - Fork 129
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
Feature: malware report #925
Comments
There is no button, we do document how to report a package: https://jsr.io/docs/usage-policy#reporting-violations. We could add a |
In my opinion, it's easier to have a modal that opens with a choice of what's causing the problem. And a free text field. |
@AugustinMauroy we would like to move messaging to something more like what you are describing, but other things (like increasing scope limits etc) are currently all done via mail, so this should stick to that until we rework messaging/tickets handling |
Also the fact of having a modal but a structure and all the relationships are the same. I totally understand, what if we did the modal but it generated an email in the back. Knowing that we have the user's email via SSO.
If not, a simple mailto is easier. maybe open pr with that but keep this issue open |
There are no button obious way to report a package on JSR. We must have that.
Also we need a page/api that list packages marked as malware so user have ability to know if there had installed malicious package.
The text was updated successfully, but these errors were encountered: