You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Like #7198, we'll need a schedule-based malware check for proofing.
The current proposal: a scheduled check for complete turnovers (i.e., no original or previous maintainers/role-holders remaining) in package ownership, graded against other suspicious indicators (IPs not previously seen for the package and/or its maintainers, new maintainers(s) are not in the community of any the the previous maintainers beyond a fixed window).
Like #7198, we'll need a schedule-based malware check for proofing.
The current proposal: a scheduled check for complete turnovers (i.e., no original or previous maintainers/role-holders remaining) in package ownership, graded against other suspicious indicators (IPs not previously seen for the package and/or its maintainers, new maintainers(s) are not in the community of any the the previous maintainers beyond a fixed window).
See #7096.
The text was updated successfully, but these errors were encountered: