@cucumber/junit-xml-formatter
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Legitimate Cucumber ecosystem formatter; sparse README/keywords are cosmetic, not spam indicators. | ai | |
| phantom-deps | phantom-dep:@teppeis/multimaps | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires because it's referenced indirectly, not a real concern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.13.3 | 4 / 27 | |
| 0.13.2 | 4 / 27 | |
| 0.9.0 | 4 / 26 | |
| 0.8.1 | 4 / 26 | |
| 0.8.0 | 4 / 24 |
v0.13.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.