karma-firefox-launcher MIT 21 versions

karma-firefox-launcher

npm Repository Homepage

A Karma plugin. Launcher for Firefox.

21

Versions

MIT

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

dignifiedquirezzovojtajinakarmarunnerbot

Keywords

karmatestingkarma-pluginkarma-launcherfirefox

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate transition from individual maintainer to karma-runner org bot account (karmarunnerbot); both are established karma ecosystem publishers.	ai	2026/04/24
semgrep	semgrep:child-process-import	AI (semgrep): Browser launcher fundamentally requires child_process to spawn Firefox; this is core functionality, not suspicious.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Published in 2019, before Sigstore provenance was available. Stable false positive for older versions.	ai	2026/04/24

Versions (showing 21 of 21)

Version	Deps	Published
2.1.3	2 / 12	2024-03-03
2.1.2	2 / 12	2021-11-02
2.1.1	2 / 11	2021-06-02
2.1.0	2 / 11	2020-11-03
2.0.0	2 / 11	2020-10-20
1.3.0	1 / 5	2020-01-08
1.2.0	1 / 5	2019-08-09
1.1.0	0 / 5	2017-12-07
1.0.1	0 / 5	2017-03-04
1.0.0	0 / 4	2016-05-04
0.1.7	0 / 4	2015-11-12
0.1.6	0 / 4	2015-05-11
0.1.5	1 / 4	2015-05-09
0.1.4	0 / 4	2014-12-29
0.1.3	0 / 4	2013-12-26
0.1.2	0 / 4	2013-11-29
0.1.1	0 / 4	2013-11-27
0.1.0	0 / 4	2013-08-06
0.0.3	0 / 4	2013-07-05
0.0.2	0 / 0	2013-05-12
0.0.1	0 / 0	2013-03-19

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.2

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.3.0

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

2 findings

HIGH Publisher changed: dignifiedquire → karmarunnerbot (on 2019-08-09) provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.0

2 findings

HIGH Publisher changed: dignifiedquire → zzo (on 2016-05-04) provenance

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