@polymarket/builder-relayer-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 — 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tsx | AI (phantom-deps): tsx is a build/runtime tool referenced in config; not a direct import pattern for this package type. | ai | |
| phantom-deps | phantom-dep:ethers | AI (phantom-deps): ethers is a transitive/type dependency used via builder-abstract-signer; phantom-dep is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): typescript is a build tool; not expected to be directly imported in runtime code. | ai | |
| phantom-deps | phantom-dep:browser-or-node | AI (phantom-deps): browser-or-node likely used indirectly via bundled/compiled output; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.0.9 | 8 / 16 | |
| 0.0.6 | 8 / 16 | |
| 0.0.5 | 8 / 16 | |
| 0.0.4 | 8 / 16 | |
| 0.0.3 | 8 / 16 | |
| 0.0.2 | 8 / 16 | |
| 0.0.1 | 8 / 16 |
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.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.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.