karma-phantomjs-launcher
A Karma plugin. Launcher for PhantomJS.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:phantomjs | AI (dependencies): phantomjs is the core dependency of this PhantomJS launcher plugin; depending on it is the package's explicit purpose and stable across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Karma launcher plugins are intentionally tiny and minimal by design; short README and small payload are expected for this plugin pattern. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition: dignifiedquire (Friedel Ziegelmayer) is a listed contributor in the karma-runner project and a well-established npm publisher. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2016, before Sigstore provenance existed. Expected for this era of packages. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.0.4 | 2 / 15 | |
| 1.0.3 | 2 / 15 | |
| 1.0.2 | 2 / 15 | |
| 1.0.1 | 2 / 15 | |
| 1.0.0 | 1 / 16 | |
| 0.2.3 | 1 / 16 | |
| 0.2.2 | 1 / 16 | |
| 0.2.1 | 1 / 14 | |
| 0.2.0 | 1 / 14 | |
| 0.1.0 | 1 / 4 | |
| 0.0.2 | 1 / 4 | |
| 0.0.1 | 0 / 0 |
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsThis version was published by a different npm account than previous versions on 2016-08-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-06-23. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-08-05. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-05-29. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.