Vibeleaderboard
← All Intel
Intel / blog

Secret protection must scale with software

Source
github.blog
Author
Erin Havens
Date

Context

GitHub argues that leaked credentials are rising because there is more code, not because developers are getting careless. In its essay, GitHub says screened public pushes grew 2.84 times between the second quarters of 2024 and 2026, while pushes carrying credentials grew 2.59 times. Across nine quarters it found no statistically detectable trend in the share of pushes with a , and the share of push-protection blocks that developers overrode fell from 6.63 to 3.93 percent.

The essay says one in three pull requests now involves an , up from fewer than one in ten a year earlier, so protection has to work before a leak is pushed. GitHub describes a classifier built with Microsoft Applied Sciences that judges candidate secrets without recognizable formats in under two milliseconds, and says it makes it possible to more than double the secrets it can prevent.

The data are GitHub's own, and the essay gives no precision or recall figures for the classifier.

Terms in this piece · Glossary
  • Secret — A value such as a password, key or token that lets its holder act as someone; it must be kept out of code and shared files.
  • Agent — A system in which a model repeatedly chooses operations, a harness carries them out, and the results return to the model to inform its next choice.
Read the source github.blog
Recommended reads
Comments

Checking sign-in…

Loading comments…