PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Reputation, Signal & Impact Calculation Enhancements

hackerone.com | blog | #bug-bounty | #hackerone | #platform-updates | #reputation | #signal | #impact
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

HackerOne is updating how Reputation, Signal, and Impact are calculated, improving accuracy, prioritizing recent performance, and easing concerns over reports marked Informative.
Published
Collected

Related coverage

blog · hackerone.com
Expanding Reputation: Introducing Signal and Impact
HackerOne expands its Reputation system with two dimensions: Signal — average reputation per report — and Impact — average reputation per bounty — to better distinguish quality from volume.
blog · hackerone.com
Improving Signal Over 10,000 Bugs
Celebrating 10,000 resolved bugs, HackerOne explains how it defines signal and lifts it — Reputation and rate limiting pushed its clear-signal rate to roughly twice Google's.
vulnerability · hackerone.com
Introducing Reputation
HackerOne launches its Reputation system to separate signal from noise: researchers gain or lose points as reports resolve, duplicate or fail, helping teams surface quality reports faster.
blog · hackerone.com
Measuring The Fix: How We Evaluate Frontier Models on Remediation Quality
HackerOne tested frontier models on security fix quality and found the judge mattered more than the model. See how CTEM remediation earns engineer trust.
blog · hackerone.com
Critical PHP Vulnerabilities: What Security Teams Need to Know
Learn about the critical PHP vulnerabilities, HackerOne’s response, and the rise in reports. Review patching guidance and coordinated disclosure practices.
blog · hackerone.com
Project Glasswing: What We Learned Running a Frontier Model on Our Own Codebase
HackerOne ran Anthropic's Mythos 5 model against its own production code; it surfaced a critical RCE spanning three safe-in-isolation commits, illustrating compositional risk that diff review misses.
Back