Skip to content

Sxing2/CLIP-Test-time-Counterattacks

View on GitHub ↗Related repositories →

[CVPR-25🔥] Test-time Counterattacks (TTC) towards adversarial robustness of CLIP

active 2025-03-012026-01-06 (UTC)

Complete coverage26,643 / 26,643 hourly files (100%) · 2 absent upstream2023-08-152026-08-29 (UTC)
Events
105
Pushes
67
Pull requests
0
Issues
3
Stars
29
Forks
3

Activity over time

Daily event counts in the loaded window

Line chart, 312 days from 2025-03-01 to 2026-01-06. Pushes: 67 total, peak 20 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 3 total, peak 2 in a day. Comments: 2 total, peak 2 in a day. Stars: 29 total, peak 7 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
Sxing2696701
Chen-Ziyang3001

Recent activity

Latest issues, pull requests and releases

  • Issue#2Sxing22026-01-06 17:29
    Unable to reproduce paper values
  • Issue comment#1Chen-Ziyang2025-03-10 11:48
    Why applying the random noise to images recognized as clean ones?
  • Issue#1Chen-Ziyang2025-03-10 11:48
    Why applying the random noise to images recognized as clean ones?
  • Issue comment#1Sxing22025-03-10 11:28
    Why applying the random noise to images recognized as clean ones?
  • Issue#1Chen-Ziyang2025-03-10 08:07
    Why applying the random noise to images recognized as clean ones?

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 29 stars here means stars gained during the window, not the repo's star count.