@hapi/accept 4.0.1

HTTP Accept-* headers parsing

@hapi/accept@4.0.1 was published on 2020-02-13. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: This version has been deprecated

All @hapi/accept versions · Permanent reference to 4.0.1 · Latest release

Package specifications

Version4.0.1
License declarationBSD-3-Clause
Published2020-02-13T06:13:10.916Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size23.02 KiB
Published file count8
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories1
Resolved graph dependencies2
Repository stars55
Repository forks30

Install @hapi/accept 4.0.1

npm install @hapi/accept@4.0.1
pnpm add @hapi/accept@4.0.1
yarn add @hapi/accept@4.0.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

Known direct advisories

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review5/10 — Found 14/28 approved changesets -- score normalized to 5
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License9/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy10/10 — security policy file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness