@percy/cli
[](https://github.com/percy/cli/actions)
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @percy/cli package; Levenshtein match to 'joi' is a false positive with no plausible impersonation. | ai | |
| 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 | |
| phantom-deps | phantom-dep:@percy/cli-exec | AI (phantom-deps): Same CLI aggregator pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@percy/cli-build | AI (phantom-deps): Same CLI aggregator pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@percy/cli-config | AI (phantom-deps): Same CLI aggregator pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@percy/cli-doctor | AI (phantom-deps): Same CLI aggregator pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@percy/cli-upload | AI (phantom-deps): Same CLI aggregator pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@percy/cli-snapshot | AI (phantom-deps): Same CLI aggregator pattern; stable false positive. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 1.32.4 | 10 / 0 | |
| 1.32.3 | 10 / 0 | |
| 1.32.2 | 10 / 0 | |
| 1.32.1 | 10 / 0 | |
| 1.32.0 | 10 / 0 | |
| 1.31.14 | 10 / 0 | |
| 1.31.13 | 10 / 0 | |
| 1.31.12 | 10 / 0 | |
| 1.31.11 | 10 / 0 | |
| 1.31.10 | 10 / 0 | |
| 1.31.9 | 9 / 0 | |
| 1.31.8 | 9 / 0 | |
| 1.31.7 | 9 / 0 | |
| 1.31.6 | 9 / 0 | |
| 1.31.5 | 9 / 0 | |
| 1.31.4 | 9 / 0 | |
| 1.31.3 | 9 / 0 | |
| 1.31.2 | 9 / 0 | |
| 1.31.1 | 9 / 0 | |
| 1.31.0 | 9 / 0 | |
| 1.30.11 | 9 / 0 | |
| 1.30.10 | 9 / 0 | |
| 1.30.9 | 9 / 0 | |
| 1.30.8 | 9 / 0 | |
| 1.30.7 | 9 / 0 | |
| 1.30.6 | 9 / 0 | |
| 1.30.5 | 9 / 0 | |
| 1.30.4 | 9 / 0 | |
| 1.30.3 | 9 / 0 | |
| 1.30.2 | 9 / 0 | |
| 1.30.1 | 9 / 0 | |
| 1.30.0 | 9 / 0 | |
| 1.29.4 | 9 / 0 | |
| 1.29.3 | 9 / 0 | |
| 1.29.2 | 9 / 0 | |
| 1.29.1 | 9 / 0 | |
| 1.29.0 | 9 / 0 | |
| 1.28.9 | 9 / 0 | |
| 1.28.8 | 9 / 0 | |
| 1.28.7 | 9 / 0 | |
| 1.28.6 | 9 / 0 |
v1.32.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.