Gathering detailed insights and metrics for hapi-vary-accept
Gathering detailed insights and metrics for hapi-vary-accept
hapi pre-response handler to include Accept in the Vary header
Installations
npm install hapi-vary-acceptDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Node Version
18.17.1
NPM Version
9.6.7
Releases
6
Languages
2
JavaScript
Shell
JavaScript (93.84%)
Shell (6.16%)
Developer
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
1 Stars
1,508 Commits
2 Watchers
11 Branches
4 Contributors
Updated on Mar 17, 2025
Maintainers
1
Package Meta Information
Latest Version
3.0.3
Package Id
hapi-vary-accept@3.0.3
Unpacked Size
12.02 kB
Size
5.25 kB
File Count
14
NPM Version
9.6.7
Node Version
18.17.1
Published on
Sep 23, 2023
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
hapi-vary-accept
hapi pre-response handler to include Accept in the Vary header
Table of Contents
Motivation
Google Chrome caches only the last response for any endpoint, regardless of
content-type, which results in rendering json data instead of the rendered
page based on the html representation. These values are cached even with the
Cache-Control header set to no-cache in order to optimize operations like
navigating back or duplicating a tab.
While normally unnecessary because of configuring the headers to prevent
caching,including Accept in the Vary header does technically further inform
a client that a single endpoint responds with different responses based on the
Accept header of the request.
- https://bugs.chromium.org/p/chromium/issues/detail?id=94369
- https://bugs.chromium.org/p/chromium/issues/detail?id=108425
- https://stackoverflow.com/questions/1975416/what-is-the-function-of-the-vary-accept-http-header
Usage
Installation
:warning: This plugin does not yet support hapi v17
1$ npm install hapi-vary-accept --save
Contribution
Verification
1$ npm test
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
GitHub workflow tokens follow principle of least privilege
Details
- Warn: jobLevel 'contents' permission set to 'write': .github/workflows/node-ci.yml:32
- Warn: jobLevel 'contents' permission set to 'write': .github/workflows/release.yml:11
- Info: topLevel 'contents' permission set to 'read': .github/workflows/node-ci.yml:40
- Info: topLevel 'contents' permission set to 'read': .github/workflows/release.yml:7
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
security policy file detected
Details
- Info: security policy file detected: github.com/travi/.github/SECURITY.md:1
- Info: Found linked content: github.com/travi/.github/SECURITY.md:1
- Warn: One or no descriptive hints of disclosure, vulnerability, and/or timelines in security policy
- Info: Found text in security policy: github.com/travi/.github/SECURITY.md:1
Reason
1 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
Reason
dependency not pinned by hash detected -- score normalized to 4
Details
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/node-ci.yml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/travi/hapi-vary-accept/node-ci.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/travi/hapi-vary-accept/release.yml/master?enable=pin
- Info: 2 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 1 out of 3 third-party GitHubAction dependencies pinned
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/17 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 26 are checked with a SAST tool
Score
5.1
/10
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More