← Home

concurrently

npm Repository Homepage

Run commands concurrently

51
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

kimmobrunfeldtgustavohenke

Keywords

bashconcurrentparallelconcurrentlycommandsh

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Migrated to GitHub Actions CI/CD publishing with SLSA provenance; legitimate transition. ai
source-diff large-new-source-files AI (source-diff): Major version bump (v9→v10) with restructured dist output; expected churn. ai
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
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

Versions (showing 51 of 64)

View all versions
Version Deps Published
10.0.3 6 / 23
9.2.1 6 / 26
9.2.0 7 / 29
9.1.2 7 / 29
9.1.1 7 / 29
9.1.0 7 / 29
9.0.1 7 / 29
9.0.0 7 / 29
8.2.2 9 / 28
8.2.1 9 / 28
8.2.0 9 / 28
8.1.0 9 / 28
8.0.1 9 / 28
8.0.0 9 / 28
7.6.0 9 / 27
7.5.0 9 / 27
7.4.0 9 / 27
7.3.0 9 / 21
7.2.2 9 / 15
7.2.1 9 / 15
7.2.0 9 / 15
7.1.0 8 / 13
7.0.0 8 / 13
6.5.1 8 / 4
6.5.0 8 / 4
6.4.0 8 / 4
6.3.0 8 / 4
6.2.2 8 / 4
6.2.1 9 / 4
6.2.0 9 / 4
6.1.0 9 / 4
6.0.2 9 / 4
6.0.1 9 / 4
6.0.0 9 / 4
5.3.0 9 / 4
5.2.0 9 / 4
5.1.0 9 / 4
5.0.2 9 / 4
5.0.1 9 / 4
5.0.0 9 / 4
4.1.2 9 / 4
4.1.1 9 / 4
4.1.0 9 / 4
4.0.1 9 / 3
4.0.0 9 / 3
3.6.1 9 / 10
3.6.0 9 / 10
3.5.1 8 / 8
3.5.0 8 / 8
3.4.0 8 / 8
3.3.0 8 / 8

v10.0.3

2 findings
HIGH Publisher changed: gustavohenke → GitHub Actions (on 2026-06-02) provenance

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

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.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.