← Home

wreck

npm Repository Homepage

HTTP Client Utilities

50
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

utilitieshttpclient

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): The hueniverse→wyatt transition is the documented hapi.js maintainer handoff to Eran Hammer (wyatt); stable and expected for all versions of this package. ai

Versions (showing 50 of 50)

Version Deps Published
14.2.0 3 / 3
14.1.4 3 / 3
14.1.3 2 / 3
14.1.2 2 / 3
14.1.1 2 / 3
14.1.0 2 / 3
14.0.2 2 / 3
14.0.1 2 / 3
14.0.0 2 / 3
13.0.3 2 / 2
13.0.2 2 / 2
13.0.1 2 / 2
13.0.0 2 / 2
12.6.2 2 / 3
12.5.1 2 / 2
12.5.0 2 / 2
12.4.0 2 / 2
12.3.0 2 / 2
12.2.3 2 / 2
12.2.2 2 / 3
12.2.1 2 / 3
12.2.0 2 / 3
12.1.0 2 / 3
12.0.0 2 / 3
11.0.0 2 / 3
10.0.0 2 / 3
9.0.0 2 / 3
8.0.1 2 / 3
8.0.0 2 / 3
7.2.1 2 / 3
7.2.0 2 / 3
7.1.0 2 / 2
7.0.2 2 / 2
7.0.1 2 / 2
7.0.0 2 / 2
6.3.0 2 / 2
6.2.0 2 / 2
6.1.0 2 / 2
6.0.0 2 / 2
5.6.1 2 / 2
5.6.0 2 / 2
5.5.1 2 / 2
5.4.0 2 / 2
5.3.0 2 / 2
5.2.0 2 / 2
5.1.0 2 / 2
5.0.1 2 / 1
5.0.0 2 / 1
4.0.0 2 / 1
3.0.0 2 / 1

v14.2.0

2 findings
HIGH Publisher changed: hueniverse → wyatt (on 2019-03-05) provenance

This version was published by a different npm account than previous versions on 2019-03-05. 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.

v14.1.4

1 finding
LOW No provenance attestation provenance

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

v14.1.3

1 finding
LOW No provenance attestation provenance

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

v14.1.2

1 finding
LOW No provenance attestation provenance

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

v14.1.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wyatt → hueniverse (on 2018-10-31) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-10-31. This could indicate a legitimate maintainer transition or an account compromise.

v14.1.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: hueniverse → wyatt (on 2018-08-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-08-21. This could indicate a legitimate maintainer transition or an account compromise.

v14.0.2

1 finding
LOW No provenance attestation provenance

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

v14.0.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wyatt → hueniverse (on 2017-11-03) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-11-03. This could indicate a legitimate maintainer transition or an account compromise.

v14.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: hueniverse → wyatt (on 2017-10-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-10-21. This could indicate a legitimate maintainer transition or an account compromise.

v13.0.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wyatt → hueniverse (on 2017-09-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-09-26. This could indicate a legitimate maintainer transition or an account compromise.

v13.0.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: hueniverse → wyatt (on 2017-09-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-09-25. This could indicate a legitimate maintainer transition or an account compromise.

v13.0.1

1 finding
LOW No provenance attestation provenance

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

v13.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wyatt → hueniverse (on 2017-09-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-09-18. This could indicate a legitimate maintainer transition or an account compromise.