@percy/cli MIT 16 versions

@percy/cli

npm Repository Homepage

[![Test](https://github.com/percy/cli/workflows/Test/badge.svg)](https://github.com/percy/cli/actions)

16

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped @percy/cli package; Levenshtein match to 'joi' is a false positive with no plausible impersonation.	ai	2026/05/15
phantom-deps	phantom-dep:@percy/cli-app	AI (phantom-deps): CLI aggregator pattern; sub-packages declared as deps but loaded dynamically, not directly imported.	ai	2026/05/15
phantom-deps	phantom-dep:@percy/cli-exec	AI (phantom-deps): Same CLI aggregator pattern; stable false positive.	ai	2026/05/15
phantom-deps	phantom-dep:@percy/cli-build	AI (phantom-deps): Same CLI aggregator pattern; stable false positive.	ai	2026/05/15
phantom-deps	phantom-dep:@percy/cli-config	AI (phantom-deps): Same CLI aggregator pattern; stable false positive.	ai	2026/05/15
phantom-deps	phantom-dep:@percy/cli-doctor	AI (phantom-deps): Same CLI aggregator pattern; stable false positive.	ai	2026/05/15
phantom-deps	phantom-dep:@percy/cli-upload	AI (phantom-deps): Same CLI aggregator pattern; stable false positive.	ai	2026/05/15
phantom-deps	phantom-dep:@percy/cli-snapshot	AI (phantom-deps): Same CLI aggregator pattern; stable false positive.	ai	2026/05/15

Versions (showing 16 of 16)

Version	Deps	Published
1.31.14	10 / 0	2026-05-21
1.31.13	10 / 0	2026-04-30
1.31.12	10 / 0	2026-04-21
1.31.11	10 / 0	2026-04-01
1.31.10	10 / 0	2026-03-18
1.31.9	9 / 0	2026-03-03
1.31.8	9 / 0	2026-01-14
1.31.7	9 / 0	2025-12-31
1.31.6	9 / 0	2025-12-23
1.31.5	9 / 0	2025-12-05
1.31.4	9 / 0	2025-10-16
1.31.3	9 / 0	2025-10-10
1.31.2	9 / 0	2025-09-09
1.31.1	9 / 0	2025-07-21
1.31.0	9 / 0	2025-06-12
1.30.11	9 / 0	2025-05-20

v1.31.14

1 finding

LOW No provenance attestation provenance

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

v1.31.13

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.31.12

1 finding

LOW No provenance attestation provenance

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

v1.31.11

1 finding

LOW No provenance attestation provenance

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

v1.31.10

1 finding

LOW No provenance attestation provenance

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

v1.31.9

1 finding

LOW No provenance attestation provenance

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

v1.31.8

1 finding

LOW No provenance attestation provenance

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

v1.31.7

1 finding

LOW No provenance attestation provenance

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

v1.31.6

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.31.5

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.31.4

1 finding

LOW No provenance attestation provenance

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

v1.31.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.

v1.31.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.

v1.31.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.

v1.31.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.30.11

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.