sauce-connect-launcher — Greenflagged

A library to download and launch Sauce Connect.

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

aearlybermijlippsjohanneswuerbachjonahsssebv

Keywords

seleniumsauce connectsauce labstestinglocal tunnel

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
install-scripts	install-script:install	AI (install-scripts): sauce-connect-launcher's core purpose is downloading/launching the Sauce Connect binary; an install script to fetch the binary is expected and documented behavior for this package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change (aearly → bermi) occurred in 2014; bermi is the listed author and GitHub repo owner. Legitimate ownership transfer, not a compromise.	ai	2026/04/24
npm-metadata	bundled-binaries	AI (npm-metadata): This package's core purpose is to bundle and launch the official Sauce Connect binary. Bundled binaries are expected and stable across all versions of this package.	ai	2026/04/24
install-scripts	install-script:postinstall	AI (install-scripts): Postinstall downloads the Sauce Connect binary — core documented functionality of this package, stable across all versions.	ai	2026/04/23
semgrep	semgrep:child-process-import	AI (semgrep): Package's primary purpose is to spawn/exec the Sauce Connect binary; child_process usage is inherent and expected.	ai	2026/04/23
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require loads a versions JSON file to select the correct binary download URL — benign and expected for this package.	ai	2026/04/23

Versions (showing 40 of 40)

Version	Deps	Published
1.3.2	5 / 12	2020-05-11
1.2.4	5 / 11	2018-04-13
1.2.3	5 / 11	2017-10-29
1.2.1	5 / 11	2017-04-13
1.2.0	5 / 11	2017-01-08
0.14.0	4 / 10	2016-01-04
0.10.0	4 / 10	2015-03-16
0.9.0	4 / 10	2014-11-14
0.8.0	4 / 10	2014-11-12
0.7.1	4 / 10	2014-11-12
0.7.0	4 / 10	2014-10-26
0.6.1	4 / 10	2014-08-04
0.6.0	4 / 10	2014-07-18
0.5.2	4 / 10	2014-07-04
0.5.1	4 / 10	2014-07-02
0.5.0	4 / 10	2014-05-24
0.4.2	4 / 10	2014-04-13
0.4.1	4 / 10	2014-04-12
0.4.0	4 / 10	2014-04-11
0.3.5	4 / 10	2014-04-11
0.3.3	4 / 10	2014-03-29
0.3.2	4 / 10	2014-03-12
0.3.1	4 / 10	2014-03-03
0.3.0	4 / 10	2014-03-02
0.2.2	3 / 9	2013-09-23
0.2.1	3 / 9	2013-09-12
0.2.0	3 / 9	2013-09-06
0.1.11	3 / 9	2013-07-24
0.1.10	3 / 9	2013-07-16
0.1.9	3 / 9	2013-07-10
0.1.8	3 / 9	2013-07-09
0.1.7	3 / 9	2013-07-09
0.1.6	4 / 9	2013-07-03
0.1.5	2 / 2	2013-06-20
0.1.4	2 / 2	2013-05-30
0.1.3	2 / 2	2013-01-31
0.1.2	2 / 2	2013-01-15
0.1.1	2 / 2	2013-01-15
0.1.0	2 / 2	2012-11-30
0.0.1	2 / 2	2012-11-16

v1.3.2

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/install.js || nodejs scripts/install.js

LOW No provenance attestation provenance

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

v1.2.4

1 finding

LOW No provenance attestation provenance

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

v1.2.3

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.10.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: bermi → aearly (on 2015-03-16) provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.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: bermi → aearly (on 2014-11-12) provenance

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

v0.7.0

3 findings

HIGH Package has 'install' script install-scripts

Script: node scripts/install.js

HIGH Publisher changed: aearly → bermi (on 2014-10-26) provenance

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

v0.6.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: bermi → aearly (on 2014-08-04) provenance

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

v0.6.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: aearly → bermi (on 2014-07-18) provenance

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

v0.5.2

2 findings

HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • sc/sc-4.3-linux/bin/sc

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.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: bermi → aearly (on 2014-05-24) provenance

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

v0.4.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: bermi → aearly (on 2014-04-13) provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

2 findings

HIGH Publisher changed: aearly → bermi (on 2014-04-11) provenance

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

v0.3.5

2 findings

HIGH Publisher changed: aearly → bermi (on 2014-04-11) provenance

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

v0.3.3

2 findings

HIGH Publisher changed: aearly → bermi (on 2014-03-29) provenance

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

v0.3.2

2 findings

HIGH Publisher changed: aearly → bermi (on 2014-03-12) provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

2 findings

HIGH Publisher changed: bermi → aearly (on 2014-03-02) provenance

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

v0.2.2

2 findings

HIGH Publisher changed: aearly → bermi (on 2013-09-23) provenance

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

v0.2.1

2 findings

HIGH Publisher changed: bermi → aearly (on 2013-09-12) provenance

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

v0.2.0

2 findings

HIGH Publisher changed: bermi → aearly (on 2013-09-06) provenance

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

v0.1.11

1 finding

LOW No provenance attestation provenance

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

v0.1.10

1 finding

LOW No provenance attestation provenance

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

v0.1.9

1 finding

LOW No provenance attestation provenance

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

v0.1.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.7

2 findings

HIGH Publisher changed: aearly → bermi (on 2013-07-09) provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.