koa-compose — Greenflagged

compose Koa middleware

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

aheckmanncoderhaoxinniftylettucejuliangrubereivifjdead_horsestephenmathiesontjholowaychuktejasmanoharjongleberryfengmk2

Keywords

koamiddlewarecompose

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): dead_horse is a known koajs org co-maintainer with extensive track record (554 approved packages, 4397 days). Legitimate maintainer transition.	ai	2026/04/23
provenance	no-provenance	AI (provenance): Published in 2018, before Sigstore provenance existed. Informational only.	ai	2026/04/23

Versions (showing 16 of 16)

Version	Deps	Published
4.2.0	0 / 4	2020-09-10
4.1.0	0 / 4	2018-05-22
4.0.0	0 / 5	2017-04-13
3.2.1	1 / 6	2016-10-26
3.2.0	2 / 6	2016-10-25
3.1.0	1 / 6	2016-03-17
3.0.0	0 / 4	2015-10-22
2.5.1	0 / 4	2016-10-26
2.5.0	1 / 4	2016-10-25
2.4.0	0 / 4	2016-03-03
2.3.0	0 / 4	2014-05-02
2.2.0	1 / 4	2014-01-23
2.1.0	1 / 4	2013-12-22
2.0.1	1 / 3	2013-12-22
2.0.0	1 / 3	2013-11-08
1.0.0	0 / 0	2013-08-13

v4.2.0

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: dead_horse → niftylettuce (on 2020-09-10) provenance

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

v4.1.0

2 findings

HIGH Publisher changed: jongleberry → dead_horse (on 2018-05-22) provenance

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

v4.0.0

1 finding

INFO No provenance attestation provenance

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

v3.2.1

1 finding

INFO No provenance attestation provenance

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

v3.2.0

1 finding

INFO No provenance attestation provenance

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

v3.1.0

1 finding

INFO No provenance attestation provenance

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

v3.0.0

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: tjholowaychuk → jongleberry (on 2015-10-22) provenance

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