Skip to content

worker/typosquat: Improve typosquat logging #11888

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 17, 2025
Merged

worker/typosquat: Improve typosquat logging #11888

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion src/worker/jobs/typosquat.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,14 @@ async fn check(
if !squats.is_empty() {
// Well, well, well. For now, the only action we'll take is to e-mail people who
// hopefully care to check into things more closely.
info!(?squats, "Found potential typosquatting");

let squats_formatted = squats
.iter()
.map(ToString::to_string)
.collect::<Vec<_>>()
.join(", ");

info!("Found potential typosquatting by new crate `{name}`: {squats_formatted}");

let squats_data: Vec<_> = squats
.iter()
Expand Down Expand Up @@ -114,6 +121,8 @@ mod tests {

#[tokio::test]
async fn integration() -> anyhow::Result<()> {
crate::util::tracing::init_for_test();

let emails = Emails::new_in_memory();
let test_db = TestDatabase::new();
let mut conn = test_db.async_connect().await;
Expand Down