shot BSD-3-Clause 51 versions

shot

npm Repository Homepage

Injects a fake HTTP request/response into a node HTTP server

51

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

hueniversemarsupmtharrisonnlfwyatt

Keywords

utilitieshttpdebugtest

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 known hapi.js ecosystem maintainers; this reflects the documented hapi.js governance transition from hueniverse. Stable for this package.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): hueniverse, mtharrison, wyatt stepping down is consistent with the well-known hapi.js project handoff. Not indicative of a takeover.	ai	2026/04/24
publish-pattern	dormant-publish	AI (publish-pattern): v3.5.2 is a legacy branch maintenance release; dormancy on older major versions is expected when active development moves to newer majors.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from hueniverse to mtharrison occurred in Feb 2018 as part of a documented hapijs org maintainer transition. mtharrison is a known hapijs contributor with 48 approved packages. This is a stable historical fact, not a new risk signal.	ai	2026/04/24

Versions (showing 51 of 68)

View all versions

Version	Deps	Published
4.0.7	2 / 2	2018-11-03
4.0.6	2 / 2	2018-11-01
4.0.5	2 / 2	2018-02-15
4.0.4	2 / 2	2017-11-14
4.0.3	2 / 2	2017-10-22
4.0.2	2 / 2	2017-10-04
4.0.1	2 / 2	2017-09-28
4.0.0	2 / 2	2017-09-23
3.5.2	2 / 2	2024-01-06
3.4.2	2 / 2	2017-06-01
3.4.1	2 / 2	2017-06-01
3.4.0	2 / 2	2016-11-29
3.3.2	2 / 2	2016-09-09
3.3.1	2 / 2	2016-08-26
3.3.0	1 / 2	2016-08-26
3.2.1	1 / 2	2016-08-26
3.2.0	0 / 2	2016-08-23
3.1.1	0 / 2	2016-07-28
3.1.0	0 / 2	2016-06-03
3.0.1	0 / 2	2016-02-09
3.0.0	1 / 2	2015-12-30
2.0.1	1 / 2	2015-11-02
1.7.0	1 / 2	2015-10-05
1.6.1	1 / 2	2015-09-24
1.6.0	1 / 2	2015-08-04
1.5.3	1 / 2	2015-06-05
1.5.2	1 / 2	2015-06-05
1.5.1	1 / 2	2015-06-04
1.5.0	1 / 2	2015-04-14
1.4.2	1 / 2	2015-03-05
1.4.1	1 / 1	2015-02-19
1.4.0	0 / 1	2014-11-24
1.3.5	0 / 1	2014-09-05
1.3.4	0 / 1	2014-08-02
1.3.3	0 / 1	2014-05-01
1.3.2	0 / 1	2014-03-08
1.3.1	0 / 1	2014-02-25
1.3.0	0 / 1	2014-01-08
1.2.0	0 / 1	2013-12-22
1.1.1	0 / 1	2013-09-29
1.1.0	0 / 1	2013-09-03
1.0.0	0 / 1	2013-08-28
0.4.5	0 / 2	2013-05-25
0.4.4	0 / 2	2013-05-18
0.4.3	0 / 2	2013-05-14
0.4.2	0 / 2	2013-05-13
0.4.1	0 / 2	2013-05-13
0.4.0	0 / 2	2013-05-11
0.3.0	0 / 2	2013-05-06
0.2.2	0 / 2	2013-04-21
0.2.1	0 / 2	2013-04-07

v4.0.7

1 finding

LOW No provenance attestation provenance

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

v4.0.6

1 finding

LOW No provenance attestation provenance

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

v4.0.5

2 findings

HIGH Publisher changed: hueniverse → mtharrison (on 2018-02-15) provenance

This version was published by a different npm account than previous versions on 2018-02-15. 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.

v4.0.4

1 finding

LOW No provenance attestation provenance

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

v4.0.3

1 finding

LOW No provenance attestation provenance

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

v4.0.2

1 finding

LOW No provenance attestation provenance

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

v4.0.1

1 finding

LOW No provenance attestation provenance

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

v4.0.0

2 findings

HIGH Publisher changed: mtharrison → hueniverse (on 2017-09-23) provenance

This version was published by a different npm account than previous versions on 2017-09-23. 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.

v3.5.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 → nargonath (on 2024-01-06) provenance

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

v3.4.2

1 finding

LOW No provenance attestation provenance

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

v3.4.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: hueniverse → mtharrison (on 2017-06-01) provenance

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

v3.4.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: mtharrison → hueniverse (on 2016-11-29) provenance

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

v3.3.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 → mtharrison (on 2016-09-09) provenance

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

v3.3.1

1 finding

LOW No provenance attestation provenance

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

v3.3.0

1 finding

LOW No provenance attestation provenance

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

v3.2.1

1 finding

LOW No provenance attestation provenance

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

v3.2.0

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

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: mtharrison → hueniverse (on 2016-07-28) provenance

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

v3.1.0

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

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 → mtharrison (on 2015-12-30) provenance

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