@percy/agent
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:sinon | AI (phantom-deps): sinon is a testing utility; declared in dependencies and referenced in test configs as expected. | ai | |
| phantom-deps | phantom-dep:@types/sinon | AI (phantom-deps): TypeScript type definitions for sinon; framework-scoped package loaded by convention. | ai | |
| phantom-deps | phantom-dep:@oclif/config | AI (phantom-deps): oclif framework dependency; referenced in oclif config block and loaded by convention. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): TypeScript type definitions for express; framework-scoped package loaded by convention. | ai | |
| phantom-deps | phantom-dep:@types/puppeteer | AI (phantom-deps): TypeScript type definitions for puppeteer; framework-scoped package loaded by convention. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): oclif plugin; referenced in oclif config block and loaded by convention. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-not-found | AI (phantom-deps): oclif plugin; referenced in oclif config block and loaded by convention. | ai |
Versions (showing 72 of 172)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 17 / 46 | |
| 0.2.2 | 17 / 47 | |
| 0.2.1 | 20 / 35 | |
| 0.2.0 | 20 / 35 | |
| 0.1.18 | 19 / 33 | |
| 0.1.17 | 19 / 33 | |
| 0.1.16 | 19 / 33 | |
| 0.1.15 | 19 / 33 | |
| 0.1.14 | 19 / 31 | |
| 0.1.13 | 19 / 31 | |
| 0.1.12 | 19 / 31 | |
| 0.1.11 | 19 / 31 | |
| 0.1.10 | 19 / 31 | |
| 0.1.9 | 19 / 31 | |
| 0.1.8 | 19 / 30 | |
| 0.1.7 | 19 / 30 | |
| 0.1.6 | 19 / 30 | |
| 0.1.5 | 19 / 30 | |
| 0.1.4 | 19 / 30 | |
| 0.1.3 | 18 / 29 | |
| 0.1.2 | 18 / 29 | |
| 0.1.1 | 18 / 29 | |
| 0.1.0 | 18 / 29 | |
| 0.0.50 | 18 / 29 | |
| 0.0.49 | 17 / 29 | |
| 0.0.48 | 17 / 29 | |
| 0.0.47 | 17 / 29 | |
| 0.0.46 | 17 / 29 | |
| 0.0.45 | 17 / 29 | |
| 0.0.44 | 17 / 29 | |
| 0.0.43 | 17 / 29 | |
| 0.0.42 | 17 / 29 | |
| 0.0.41 | 17 / 29 | |
| 0.0.40 | 16 / 29 | |
| 0.0.39 | 16 / 29 | |
| 0.0.38 | 16 / 29 | |
| 0.0.37 | 16 / 29 | |
| 0.0.36 | 16 / 29 | |
| 0.0.35 | 17 / 29 | |
| 0.0.34 | 17 / 29 | |
| 0.0.33 | 17 / 29 | |
| 0.0.32 | 17 / 29 | |
| 0.0.31 | 17 / 29 | |
| 0.0.30 | 17 / 29 | |
| 0.0.29 | 17 / 29 | |
| 0.0.28 | 17 / 29 | |
| 0.0.27 | 17 / 29 | |
| 0.0.26 | 17 / 29 | |
| 0.0.25 | 17 / 29 | |
| 0.0.24 | 17 / 29 | |
| 0.0.23 | 17 / 29 | |
| 0.0.22 | 17 / 29 | |
| 0.0.21 | 17 / 29 | |
| 0.0.20 | 15 / 29 | |
| 0.0.19 | 15 / 29 | |
| 0.0.18 | 15 / 29 | |
| 0.0.17 | 15 / 29 | |
| 0.0.16 | 15 / 29 | |
| 0.0.15 | 15 / 29 | |
| 0.0.14 | 15 / 29 | |
| 0.0.13 | 15 / 29 | |
| 0.0.12 | 15 / 29 | |
| 0.0.11 | 15 / 29 | |
| 0.0.10 | 15 / 29 | |
| 0.0.9 | 15 / 29 | |
| 0.0.8 | 15 / 29 | |
| 0.0.7 | 15 / 29 | |
| 0.0.6 | 15 / 29 | |
| 0.0.5 | 15 / 29 | |
| 0.0.4 | 15 / 29 | |
| 0.0.3 | 15 / 29 | |
| 0.0.2 | 14 / 30 |
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.