@percy/core
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @percy/core package; no relation to cors. Levenshtein match is a false positive. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Documented post-install script for Percy browser binary setup; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@percy/dom | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.31.14 | 18 / 0 | |
| 1.31.13 | 18 / 0 | |
| 1.31.7 | 17 / 0 | |
| 1.31.5 | 17 / 0 |
v1.31.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.13
3 findingsScript: node ./post-install
Package name '@percy/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.7
3 findingsScript: node ./post-install
Package name '@percy/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.5
3 findingsScript: node ./post-install
Package name '@percy/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.