@smartbear/react-gherkin-editor
A Gherkin language editor for React.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): buffer polyfill likely used indirectly in bundled build output, not a malware indicator. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-standing publisher change (2040d), inconsistent with account takeover. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.4.14 | 8 / 32 | |
| 2.3.1 | 9 / 17 | |
| 2.2.2 | 7 / 17 | |
| 2.2.1 | 7 / 17 |
v2.3.1
2 findingsThis version was published by a different npm account (aurelien.reeves) than the most recent previously approved version (timotheeville) on 2020-12-24. It has since remained available on npm for 2040 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.