@camunda/e2e-test-suite
End-to-end test helpers for Camunda 8
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Lack of provenance is common (88% of npm); not a security concern for this internal test package. | ai | |
| phantom-deps | phantom-dep:unzipper | AI (phantom-deps): Test suite dependency used in config/setup; indirect usage is normal for test utilities. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Test suite dependency used in config/setup; indirect usage is normal for test utilities. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): Test suite dependency used in config/setup; indirect usage is normal for test utilities. | ai | |
| phantom-deps | phantom-dep:@axe-core/playwright | AI (phantom-deps): Test suite dependency used in config/setup; indirect usage is normal for test utilities. | ai | |
| bogus-package | bogus-package | AI (bogus-package): README link density is consistent with an internal Camunda E2E test suite linking to docs/resources. Not a phishing indicator for this scoped package. | ai | |
| dependencies | unvetted-dep:@axe-core/playwright | AI (dependencies): @axe-core/playwright is Deque Systems' accessibility testing library, a reputable and widely-used package for E2E testing. | ai | |
| dependencies | unvetted-dep:mailslurp-client | AI (dependencies): mailslurp-client is a standard email testing API client, appropriate for E2E test suites. No malicious signals. | ai |
Versions (showing 55 of 366)
| Version | Deps | Published |
|---|---|---|
| 0.0.358 | 6 / 20 | |
| 0.0.357 | 6 / 20 | |
| 0.0.355 | 6 / 20 | |
| 0.0.354 | 6 / 20 | |
| 0.0.353 | 6 / 20 | |
| 0.0.349 | 6 / 20 | |
| 0.0.348 | 6 / 20 | |
| 0.0.346 | 6 / 20 | |
| 0.0.344 | 6 / 20 | |
| 0.0.343 | 6 / 20 | |
| 0.0.342 | 6 / 20 | |
| 0.0.337 | 6 / 20 | |
| 0.0.336 | 6 / 20 | |
| 0.0.333 | 6 / 20 | |
| 0.0.332 | 6 / 20 | |
| 0.0.330 | 6 / 20 | |
| 0.0.325 | 6 / 20 | |
| 0.0.322 | 6 / 20 | |
| 0.0.320 | 6 / 20 | |
| 0.0.319 | 6 / 20 | |
| 0.0.318 | 6 / 20 | |
| 0.0.317 | 6 / 20 | |
| 0.0.316 | 6 / 20 | |
| 0.0.313 | 6 / 20 | |
| 0.0.310 | 6 / 20 | |
| 0.0.307 | 6 / 20 | |
| 0.0.306 | 6 / 20 | |
| 0.0.305 | 6 / 20 | |
| 0.0.302 | 6 / 20 | |
| 0.0.298 | 6 / 20 | |
| 0.0.297 | 6 / 20 | |
| 0.0.296 | 6 / 20 | |
| 0.0.294 | 6 / 20 | |
| 0.0.292 | 6 / 20 | |
| 0.0.291 | 6 / 20 | |
| 0.0.289 | 6 / 20 | |
| 0.0.286 | 6 / 20 | |
| 0.0.214 | 6 / 20 | |
| 0.0.20 | 4 / 18 | |
| 0.0.16 | 4 / 18 | |
| 0.0.15 | 4 / 18 | |
| 0.0.14 | 4 / 18 | |
| 0.0.13 | 4 / 18 | |
| 0.0.12 | 4 / 18 | |
| 0.0.11 | 4 / 18 | |
| 0.0.10 | 4 / 18 | |
| 0.0.9 | 4 / 18 | |
| 0.0.8 | 4 / 18 | |
| 0.0.7 | 4 / 18 | |
| 0.0.6 | 4 / 18 | |
| 0.0.5 | 4 / 18 | |
| 0.0.4 | 4 / 18 | |
| 0.0.3 | 4 / 18 | |
| 0.0.2 | 4 / 18 | |
| 0.0.1 | 4 / 18 |
v0.0.214
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.