@hapi/wreck
HTTP Client Utilities
78%
Total Score
75
100
94
83
Health Score Breakdown
There were no commits or active maintainers in the last three months, which is a maintenance caution, though the recent registry release and August repository push provide compensating evidence.
The repository uses TypeScript build tooling, but no security scanning tools were detected; this is a modest transparency and hygiene gap rather than a release-blocking concern.
The single workflow was fully audited with no dangerous sinks or audit findings. Its one action is unpinned, which is a minor reproducibility and supply-chain hygiene concern.
Vulnerabilities
| Title | Versions | Severity |
|---|---|---|
CVE-2026-48022 @hapi/wreck is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor in versions 0.0.0 - 18.1.2. | 0.0.0 - 18.1.2 | Medium |
CVE-2026-44979 @hapi/wreck is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor in versions 0.0.0 - 18.1.1. | 0.0.0 - 18.1.1 | Medium |
Package versions
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 @hapi/boom Version ^10.0.1 | — | — |
@hapi/hoek Version ^11.0.2 | — | — |
@hapi/bourne Version ^3.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 months ago
- Created
- 7 years ago
- Unpacked Size
- 0.1 MB
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.