artillery-engine-playwright
⚠️ *This plugin is bundled into Artillery itself. Do not install it separately.*
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@playwright/test | AI (phantom-deps): Runtime dependency for Playwright engine; correctly declared and used. | ai | |
| phantom-deps | phantom-dep:@playwright/browser-chromium | AI (phantom-deps): Runtime dependency for Playwright engine; correctly declared and used. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.29.0 | 4 / 2 | |
| 1.28.0 | 4 / 2 | |
| 1.27.0 | 4 / 2 | |
| 1.26.0 | 4 / 2 | |
| 1.25.0 | 4 / 2 | |
| 1.24.0 | 4 / 2 | |
| 1.23.0 | 4 / 2 | |
| 1.22.0 | 4 / 2 | |
| 1.21.0 | 4 / 2 | |
| 1.20.0 | 4 / 2 |
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.