accept BSD-3-Clause 16 versions

accept

npm Repository Homepage

HTTP Accept-* headers parsing

16

Versions

BSD-3-Clause

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

hueniversemarsupnlfwyatt

Keywords

HTTPheaderacceptaccept-encoding

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): nargonath and devinivy are established hapi.js core maintainers; legitimate transition.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): hueniverse/wyatt removal is part of documented hapi ecosystem maintainer transition.	ai	2026/04/24
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy explained by old major version line receiving maintenance update after project transition.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from hueniverse to markbradshaw occurred in 2016 and reflects a known hapijs maintainer transition. markbradshaw has 15 approved packages and no rejections; this is a stable historical fact for this package.	ai	2026/04/24

Versions (showing 16 of 16)

Version	Deps	Published
3.1.3	2 / 2	2018-11-03
3.1.2	2 / 2	2018-11-01
3.1.1	2 / 2	2018-10-30
3.0.2	2 / 2	2017-11-03
3.0.1	2 / 3	2017-09-26
3.0.0	2 / 3	2017-09-25
2.2.3	2 / 2	2024-01-01
2.1.4	2 / 3	2017-05-28
2.1.3	2 / 3	2016-09-07
2.1.2	2 / 3	2016-07-27
2.1.1	2 / 2	2016-05-06
2.1.0	2 / 2	2015-12-22
2.0.0	2 / 2	2015-11-01
1.1.0	2 / 2	2015-07-09
1.0.0	2 / 1	2014-10-03
0.0.0	2 / 1	2014-10-03

v3.1.3

1 finding

LOW No provenance attestation provenance

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

v3.1.2

1 finding

LOW No provenance attestation provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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

v2.2.3

2 findings

HIGH Publisher changed: hueniverse → nargonath (on 2024-01-01) provenance

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.

LOW No provenance attestation provenance

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

v2.1.4

2 findings

HIGH Publisher changed: markbradshaw → hueniverse (on 2017-05-28) provenance

This version was published by a different npm account than previous versions on 2017-05-28. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.1.3

2 findings

HIGH Publisher changed: hueniverse → markbradshaw (on 2016-09-07) provenance

This version was published by a different npm account than previous versions on 2016-09-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.1.2

1 finding

LOW No provenance attestation provenance

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

v2.1.1

2 findings

HIGH Publisher changed: hueniverse → markbradshaw (on 2016-05-06) provenance

This version was published by a different npm account than previous versions on 2016-05-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.1.0

2 findings

HIGH Publisher changed: hueniverse → markbradshaw (on 2015-12-22) provenance

This version was published by a different npm account than previous versions on 2015-12-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.0

2 findings

HIGH Publisher changed: markbradshaw → hueniverse (on 2015-11-01) provenance

This version was published by a different npm account than previous versions on 2015-11-01. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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