@percy/client
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Percy org package; absence of provenance is consistent across all their releases. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 1.32.5 | 5 / 0 | |
| 1.32.4 | 5 / 0 | |
| 1.32.3 | 5 / 0 | |
| 1.32.2 | 5 / 0 | |
| 1.32.1 | 5 / 0 | |
| 1.32.0 | 5 / 0 | |
| 1.31.14 | 5 / 0 | |
| 1.31.13 | 5 / 0 | |
| 1.31.12 | 5 / 0 | |
| 1.31.11 | 5 / 0 | |
| 1.31.10 | 5 / 0 | |
| 1.31.9 | 5 / 0 | |
| 1.31.8 | 5 / 0 | |
| 1.31.7 | 5 / 0 | |
| 1.31.6 | 5 / 0 | |
| 1.31.5 | 5 / 0 | |
| 1.31.4 | 5 / 0 | |
| 1.31.3 | 5 / 0 | |
| 1.31.2 | 5 / 0 | |
| 1.31.1 | 4 / 0 | |
| 1.31.0 | 4 / 0 | |
| 1.30.11 | 4 / 0 | |
| 1.30.10 | 4 / 0 | |
| 1.30.9 | 4 / 0 | |
| 1.30.8 | 4 / 0 | |
| 1.30.7 | 4 / 0 | |
| 1.30.6 | 3 / 0 | |
| 1.30.5 | 3 / 0 | |
| 1.30.4 | 3 / 0 | |
| 1.30.3 | 3 / 0 | |
| 1.30.2 | 3 / 0 | |
| 1.30.1 | 3 / 0 | |
| 1.30.0 | 3 / 0 | |
| 1.29.4 | 3 / 0 | |
| 1.29.3 | 3 / 0 | |
| 1.29.2 | 3 / 0 | |
| 1.29.1 | 3 / 0 | |
| 1.29.0 | 3 / 0 | |
| 1.28.9 | 3 / 0 | |
| 1.28.8 | 3 / 0 | |
| 1.28.7 | 3 / 0 | |
| 1.28.6 | 3 / 0 |
v1.32.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.