Skip to content

Lightweight publication burst reports #10826

Open
@LawnGnome

Description

@LawnGnome

Coming out of today's team meeting: it would be nice to have some sort of reporting of recent bursts of crate publication from a single account that are technically within the rate limit, but involve a sufficient number of crates that a crates.io team member should have a quick look at the account to make sure they're not violating the guidelines.

A cron job and a well placed query should get this done. I'm thinking nightly, with reporting on the previous 48 hours, and an e-mail sent to (insert address(es)/Zulip stream here) with anything worth checking.

(In the longer term, this is the kind of thing that could feed into a dashboard, or could be part of the scoring that goes into a quarantine system, but a cron job + e-mail feels like the right level of investment right now to me.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-backend ⚙️A-infrastructure 📡A-publishC-enhancement ✨Category: Adding new behavior or a change to the way an existing feature worksC-internal 🔧Category: Nonessential work that would make the codebase more consistent or clear

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions