wdio-dot-reporter
A WebdriverIO plugin. Report results in dot format.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:coverage/lcov-report/prettify.js | AI (source-diff): This is the standard Google Code Prettify minified JS included in Istanbul/lcov HTML coverage reports — a benign build artifact, not malicious obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is entirely due to committed lcov coverage report artifacts, not injected payloads. | ai | |
| provenance | no-provenance | AI (provenance): Package is ~10 years old; provenance attestation was not available at publish time. Expected for this package's age. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.0.10 | 0 / 21 | |
| 0.0.9 | 0 / 21 | |
| 0.0.8 | 0 / 19 | |
| 0.0.7 | 1 / 23 | |
| 0.0.6 | 1 / 23 | |
| 0.0.5 | 1 / 23 | |
| 0.0.4 | 0 / 24 | |
| 0.0.3 | 0 / 11 | |
| 0.0.2 | 0 / 11 | |
| 0.0.1 | 0 / 11 |
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
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.