Work at LibSass? Claim it to respond to reviews as the verified owner.
Found a vulnerability?
If you would rather not deal with the vendor yourself, a BugRater analyst will submit it upstream on your behalf, with your explicit permission, and tell you what came back.
Ask BugRater to submit itPrivate. The report body is encrypted at rest; BugRater holds the key, so the analyst working it can read it. Every read is logged.
HackerOne’s own figures for this program, read from its public page, not reported by researchers and not part of the BugRater grade. Captured 4 Oct 2026.
What it pays, by severity
Intake & responsiveness · last 90 days
Response targets it sets itself
A target the program declared, not a measurement of it being met.
Getting in the door
Over 45 days (96 snapshots): no change on the figures worth watching.
Source: HackerOne Hacktivity (public disclosures) Program: https://hackerone.com/libsass Disclosed reports analyzed: 10 Bounties: none in disclosed reports --- Aggregated from publicly disclosed HackerOne reports. Ratings derived from triage timing and bounty data.
Researchers HackerOne shows on this program’s public thanks list, best position first. “Recognised” is how many of a hunter’s submissions the program accepted; the ratio is their signal here, not our judgement of them.
| # | Researcher | Reputation | Recognised / submitted |
|---|---|---|---|
| 1 | geeknik | 63 | 9 / 13 69% |
| 2 | karas | 56 | 8 / 8 100% |
| 3 | mrtuxracer | 35 | 5 / 5 100% |
| 4 | flamezzz | 14 | 2 / 2 100% |
| 4 | hongphi_pham95 | 14 | 2 / 2 100% |
| 6 | richo | 7 | 1 / 1 100% |
Facts published by HackerOne on the program's own page, not reported by researchers, and not part of the BugRater grade. Last checked 1 Oct 2026.
LibSass is a C/C++ port of the Sass engine. The point is to be simple, fast, and easy to integrate.
Log in to comment