@percy/cypress MIT 38 versions

@percy/cypress

npm Repository Homepage

Cypress client library for visual testing with Percy

38

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

percy-admin

Keywords

cypresspercyvisual testing

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from dgjones to percy-admin occurred in April 2019 — a legitimate org account transition. percy-admin has 368 approved packages and is the canonical Percy org account.	ai	2026/04/24
semgrep	semgrep:child-process-import	AI (semgrep): child_process usage is in run-tests.js (dev test runner), not in published runtime code. Expected for a Cypress testing library's dev tooling.	ai	2026/04/23
dependencies	unvetted-dep:@percy/sdk-utils	AI (dependencies): @percy/sdk-utils is a first-party Percy SDK dependency from the same organization (Perceptual Inc.); its presence is expected and stable across all versions of this package.	ai	2026/04/23
semgrep	semgrep:eval-usage	AI (semgrep): eval() is used to inject Percy's own DOM serialization library into the Cypress browser window — a documented, stable pattern for this SDK across all versions.	ai	2026/04/23
typosquat	typosquat.levenshtein:express	AI (typosquat): @percy/cypress is a scoped Percy org package for Cypress integration, not a typosquat of express. Levenshtein match is a clear false positive.	ai	2026/04/21

Versions (showing 38 of 38)

Version	Deps	Published
3.1.8	1 / 15	2026-04-02
3.1.7	1 / 15	2025-11-24
3.1.6	1 / 15	2025-04-18
3.1.5	1 / 15	2025-03-17
3.1.4	1 / 15	2025-02-17
3.1.3	1 / 15	2024-12-11
3.1.2	1 / 15	2022-06-16
3.1.1	1 / 13	2021-07-22
3.1.0	1 / 13	2021-04-14
3.0.0	1 / 13	2021-04-01
2.3.4	2 / 8	2021-01-21
2.3.3	2 / 8	2020-12-01
2.3.2	2 / 8	2020-09-30
2.3.1	2 / 8	2020-03-05
2.3.0	2 / 8	2020-02-03
2.2.0	2 / 8	2019-10-08
2.1.1	2 / 8	2019-09-20
2.1.0	2 / 8	2019-09-17
2.0.1	2 / 8	2019-08-26
2.0.0	2 / 8	2019-08-02
1.0.9	1 / 8	2019-05-08
1.0.8	1 / 8	2019-05-02
1.0.7	1 / 8	2019-04-30
1.0.6	1 / 8	2019-04-09
1.0.5	1 / 5	2019-04-03
1.0.4	1 / 5	2019-03-27
1.0.3	1 / 5	2019-03-21
1.0.2	1 / 5	2019-02-14
1.0.1	1 / 5	2019-02-12
1.0.0	1 / 5	2019-02-07
0.2.3	1 / 3	2018-11-28
0.2.2	1 / 3	2018-11-16
0.2.1	1 / 3	2018-11-13
0.2.0	1 / 3	2018-11-07
0.1.0	1 / 3	2018-10-24
0.0.4	1 / 3	2018-10-22
0.0.3	1 / 3	2018-09-26
0.0.2	1 / 3	2018-09-25

v3.1.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.9

2 findings

HIGH Publisher changed: dgjones → percy-admin (on 2019-05-08) provenance

This version was published by a different npm account than previous versions on 2019-05-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.8

2 findings

HIGH Publisher changed: dgjones → percy-admin (on 2019-05-02) provenance

This version was published by a different npm account than previous versions on 2019-05-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.7

2 findings

HIGH Publisher changed: dgjones → percy-admin (on 2019-04-30) provenance

This version was published by a different npm account than previous versions on 2019-04-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.6

2 findings

HIGH Publisher changed: dgjones → percy-admin (on 2019-04-09) provenance

This version was published by a different npm account than previous versions on 2019-04-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.