@cypress/github-action
GitHub Action for running Cypress end-to-end and component tests
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Cypress official package; lack of provenance is consistent across all prior versions. | ai | |
| dependencies | unvetted-dep:@actions/cache | AI (dependencies): Official GitHub Actions toolkit package; stable dependency for this GitHub Action package. | ai | |
| dependencies | unvetted-dep:argument-vector | AI (dependencies): Small utility used by Cypress ecosystem; no malicious indicators, stable for this package. | ai | |
| phantom-deps | phantom-dep:@actions/core | AI (phantom-deps): ncc-bundled GitHub Action; all deps are bundled into dist/index.js, not directly imported. | ai | |
| phantom-deps | phantom-dep:@actions/exec | AI (phantom-deps): ncc-bundled GitHub Action; all deps are bundled into dist/index.js, not directly imported. | ai | |
| phantom-deps | phantom-dep:@octokit/core | AI (phantom-deps): ncc-bundled GitHub Action; all deps are bundled into dist/index.js, not directly imported. | ai | |
| phantom-deps | phantom-dep:hasha | AI (phantom-deps): ncc-bundled GitHub Action; all deps are bundled into dist/index.js, not directly imported. | ai | |
| phantom-deps | phantom-dep:supports-color | AI (phantom-deps): ncc-bundled GitHub Action; all deps are bundled into dist/index.js, not directly imported. | ai | |
| phantom-deps | phantom-dep:argument-vector | AI (phantom-deps): ncc-bundled GitHub Action; all deps are bundled into dist/index.js, not directly imported. | ai | |
| phantom-deps | phantom-dep:find-yarn-workspace-root | AI (phantom-deps): ncc-bundled GitHub Action; all deps are bundled into dist/index.js, not directly imported. | ai | |
| phantom-deps | phantom-dep:@actions/cache | AI (phantom-deps): ncc-bundled GitHub Action; all deps are bundled into dist/index.js, not directly imported. | ai | |
| phantom-deps | phantom-dep:quote | AI (phantom-deps): ncc-bundled GitHub Action; all deps are bundled into dist/index.js, not directly imported. | ai | |
| phantom-deps | phantom-dep:@actions/io | AI (phantom-deps): ncc-bundled GitHub Action; all deps are bundled into dist/index.js, not directly imported. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 12 / 10 | |
| 7.1.10 | 12 / 10 | |
| 7.1.9 | 12 / 10 | |
| 7.1.7 | 12 / 10 | |
| 7.1.6 | 12 / 10 | |
| 7.1.4 | 12 / 10 | |
| 7.1.1 | 12 / 10 | |
| 6.10.8 | 12 / 10 | |
| 6.10.6 | 12 / 10 | |
| 6.10.5 | 12 / 10 | |
| 6.10.4 | 12 / 10 |
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.