← Home

vary

npm Repository Homepage

Manipulate the HTTP Vary header

7
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

dougwilson

Keywords

httpresvary

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): [email protected] is a legitimate early release by a trusted Express.js maintainer with 72.9M weekly downloads. The 0.0.0 version is not indicative of malicious intent here. ai
provenance no-provenance AI (provenance): Package predates npm provenance attestation by many years; absence of provenance is expected and not a risk signal for this package. ai

Versions (showing 7 of 7)

Version Deps Published
1.1.2 0 / 12
1.1.1 0 / 8
1.1.0 0 / 3
1.0.1 0 / 3
1.0.0 0 / 4
0.1.0 0 / 3
0.0.0 0 / 3

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.