Analysis updated 2026-07-16 · repo last pushed 2018-12-30
Add a breach warning feature to a password manager so users know if their credentials were exposed.
Build a security audit tool that checks employee email addresses against known data breaches.
Create an app that alerts users when their email appears in a new data breach.
| eternal-flame-ad/hibp | aasheeshlikepanner/vase | alexzielenski/controller-runtime | |
|---|---|---|---|
| Stars | — | 0 | — |
| Language | Go | Go | Go |
| Last pushed | 2018-12-30 | — | 2022-04-20 |
| Maintenance | Dormant | — | Dormant |
| Setup difficulty | moderate | moderate | hard |
| Complexity | 2/5 | 4/5 | 4/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
No usage examples or setup instructions in the README, developer must read godoc or source to learn the API, and a Have I Been Pwned API key is required.
This project is a small package that lets Go programs talk to the Have I Been Pwned service. Have I Been Pwned is a well-known website where people can check whether their email address or password has appeared in a known data breach. Instead of a developer manually making web requests and parsing responses, this package handles that interaction so they can focus on using the results. At a high level, the package wraps the Have I Been Pwned API in Go code. A developer imports it into their project, provides an API key or query parameters, and calls functions that return structured data, like which breaches an email address appears in. The package abstracts away the HTTP requests and JSON parsing, giving back Go objects that are straightforward to work with in a program. Someone building a security-related application would find this useful. For example, a developer creating a password manager could use it to warn users if their credentials have been exposed in a breach. A startup building a tool that audits organizational security might use it to check employee email addresses against known breaches. It saves those teams from writing boilerplate code to communicate with the service directly. The README is very minimal, just a link to the documentation and a few badges indicating build status and test coverage. There are no usage examples or setup instructions included, so a developer would need to look at the godoc page or read the source to understand the available functions and how to call them. The project itself is straightforward: a focused utility that does one thing for the Go ecosystem.
A Go package that lets programs check email addresses and passwords against the Have I Been Pwned breach database. It handles the API requests and data parsing so developers can focus on using the results.
Mainly Go. The stack also includes Go, Have I Been Pwned API.
Dormant — no commits in 2+ years (last push 2018-12-30).
No license information is provided in the README, so usage rights are unclear without checking the repository further.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.