elliotjreed/haveibeenpwned
The repository has no security policy or scanning, and both workflow actions are unpinned. Clear documentation, tests, licensing, and recent commits provide useful safeguards.
79%
Total Score
67
100
94
67
Health Score Breakdown
The repository is owned by an individual user rather than an organization, so the concentrated recent activity is not offset by visible organizational handoff capacity.
All four recent commits came from one contributor, and the contributor count for the period is one. This creates a real continuity risk for a user-owned project.
Composer and Make are used for builds, but no security-scanning tooling is present. That is a maintenance and review gap, though the repository still has visible build structure and tests.
The repository has no security policy. This weakens transparency around vulnerability reporting and response for a package that handles an external API.
The single workflow was fully analyzed with no audit findings or unsafe triggers, but both of its two action references are unpinned. The missing top-level permissions block is acceptable on its own, while unpinned actions remain a modest reproducibility risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Elliot Reed |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.0|^8.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 5 years ago
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.