concurrently — Greenflagged

Run commands concurrently

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

kimmobrunfeldtgustavohenke

Keywords

bashconcurrentparallelconcurrentlycommandsh

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): concurrently is a long-established package with a trusted publisher; missing gitHead reflects a CI/CD tooling change, not a security concern.	ai	2026/04/24
provenance	no-provenance	AI (provenance): concurrently is a long-established, trusted package; lack of Sigstore provenance is a best-practice gap, not a security risk for this package.	ai	2026/04/24

Versions (showing 51 of 63)

View all versions

Version	Deps	Published
9.2.1	6 / 26	2025-08-25
9.2.0	7 / 29	2025-06-22
9.1.2	7 / 29	2024-12-31
9.1.1	7 / 29	2024-12-27
9.1.0	7 / 29	2024-11-04
9.0.1	7 / 29	2024-09-12
9.0.0	7 / 29	2024-09-08
8.2.2	9 / 28	2023-10-19
8.2.1	9 / 28	2023-08-22
8.2.0	9 / 28	2023-06-09
8.1.0	9 / 28	2023-06-01
8.0.1	9 / 28	2023-03-29
8.0.0	9 / 28	2023-03-28
7.6.0	9 / 27	2022-11-20
7.5.0	9 / 27	2022-10-22
7.4.0	9 / 27	2022-09-07
7.3.0	9 / 21	2022-07-18
7.2.2	9 / 15	2022-06-14
7.2.1	9 / 15	2022-05-22
7.2.0	9 / 15	2022-05-15
7.1.0	8 / 13	2022-04-02
7.0.0	8 / 13	2022-01-03
6.5.1	8 / 4	2021-12-19
6.5.0	8 / 4	2021-12-17
6.4.0	8 / 4	2021-11-13
6.3.0	8 / 4	2021-10-02
6.2.2	8 / 4	2021-09-27
6.2.1	9 / 4	2021-08-08
6.2.0	9 / 4	2021-05-24
6.1.0	9 / 4	2021-05-08
6.0.2	9 / 4	2021-04-12
6.0.1	9 / 4	2021-04-05
6.0.0	9 / 4	2021-02-20
5.3.0	9 / 4	2020-08-07
5.2.0	9 / 4	2020-04-25
5.1.0	9 / 4	2020-01-27
5.0.2	9 / 4	2019-12-18
5.0.1	9 / 4	2019-12-09
5.0.0	9 / 4	2019-10-07
4.1.2	9 / 4	2019-08-16
4.1.1	9 / 4	2019-06-25
4.1.0	9 / 4	2018-11-18
4.0.1	9 / 3	2018-08-26
4.0.0	9 / 3	2018-08-24
3.6.1	9 / 10	2018-07-24
3.6.0	9 / 10	2018-06-19
3.5.1	8 / 8	2017-11-21
3.5.0	8 / 8	2017-06-22
3.4.0	8 / 8	2017-03-02
3.3.0	8 / 8	2017-02-12
3.2.0	8 / 8	2017-02-08

v9.2.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v9.2.0

1 finding

LOW No provenance attestation provenance

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

v9.1.2

1 finding

LOW No provenance attestation provenance

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

v9.1.1

1 finding

LOW No provenance attestation provenance

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

v9.1.0

1 finding

LOW No provenance attestation provenance

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

v9.0.1

1 finding

LOW No provenance attestation provenance

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

v9.0.0

1 finding

LOW No provenance attestation provenance

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

v8.2.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gustavohenke.

INFO No provenance attestation provenance

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

v8.2.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gustavohenke.

INFO No provenance attestation provenance

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

v8.2.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gustavohenke.

INFO No provenance attestation provenance

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

v8.1.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gustavohenke.

LOW No provenance attestation provenance

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

v8.0.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gustavohenke.

INFO No provenance attestation provenance

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

v8.0.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gustavohenke.

INFO No provenance attestation provenance

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