ammo @2.1.2
HTTP Range processing utilities
Maintainers
Keywords
Dev Dependencies (3)
| Package | Constraint | Registry Status |
|---|---|---|
| lab | 14.x.x | auto_approved |
| code | 4.x.x | auto_approved |
| wreck | 12.x.x | auto_approved |
Transitive Dependency Tree
Changes from v1.0.1
Dependency Changes
| Change | Package | Version |
|---|---|---|
| changed | boom | 2.x.x → 5.x.x |
| changed | hoek | 2.x.x → 4.x.x |
License Changed
BSD-3-Clause → SEE LICENSE IN LICENSE.mdFile Changes
Risk Dispositions (1 applicable to this version, 0 other)
Accepted rules are downgraded to INFO on future analyses; rejected rules escalate to CRITICAL.
| Rule | Source | Disposition | Author | Reason | |
|---|---|---|---|---|---|
osv:GHSA-mg85-8mv5-ffjr |
osv | reject | AI | AI (osv): Advisory covers all versions of ammo (>= 0.0.0) with no fix; package is deprecated with no planned remediation. Verdict generalizes to every version of this package. |
SAST Findings (3)
[Always reject] All versions of `ammo` are vulnerable to Denial of Service. The Range HTTP header parser has a vulnerability which will cause the function to throw a system error if the header is set to an invalid value. Because hapi is not expecting the function to ever throw, the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services. ## Recommendation This package is deprecated and is now maintained as `@hapi/ammo`. Please update your dependencies to use `@hapi/ammo`.
This version was published by a different npm account than previous versions on 2024-01-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
Review Summary
Risk score: 100 (capped from 101). Findings: 1 critical (+40), 1 high (+25), 3 medium (+30), 2 low (+6), 1 info (+0).
Commit: 7071f8bca469 Browse source
Published to npm: