According to CoinMeta, on October 19th, GitHub announced that it would temporarily add identity authentication for download requests to certain public repositories under HTTPS. Once the system detects abnormal traffic, which normally does not require login to clone (clone) or pull (fetch) code, it may suddenly require the provision of token. Construction and automatic installation scripts that rely on anonymous downloads (CI) may also be interrupted as a result. Similar issues emerged in September, with developers reporting that when pulling from MariaDB public repositories on CI servers, they repeatedly encountered `401` errors, making it impossible to even update sub-modules. GitHub explained that the platform is facing an increasing amount of bot traffic, and normal development requests may also be misidentified. This announcement further clarifies the scope of application for the temporary authentication measures, recommending that developers configure identity authentication for automated tasks to avoid relying on anonymous HTTPS downloads. Operations that are already authenticated, such as HTTPS and SSH, are not affected by this restriction.