@polymarket/clob-client-v2
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ethers | AI (phantom-deps): Direct runtime dependency; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ethersproject/units | AI (phantom-deps): Direct runtime dependency; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Implicit transitive dependency via viem/ethers; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@ethersproject/wallet | AI (phantom-deps): Implicit transitive dependency; referenced in config but not direct import. | ai | |
| phantom-deps | phantom-dep:@ethersproject/providers | AI (phantom-deps): Implicit transitive dependency; referenced in config but not direct import. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.0.6 | 6 / 9 | |
| 1.0.5 | 6 / 9 | |
| 1.0.4 | 6 / 9 | |
| 1.0.3 | 6 / 9 | |
| 1.0.2 | 6 / 9 | |
| 1.0.1 | 6 / 9 | |
| 1.0.0 | 6 / 8 | |
| 0.2.7 | 6 / 8 | |
| 0.2.6 | 6 / 8 | |
| 0.2.5 | 6 / 8 | |
| 0.2.4 | 6 / 8 | |
| 0.2.3 | 6 / 8 | |
| 0.2.2 | 6 / 8 | |
| 0.2.1 | 6 / 8 | |
| 0.2.0 | 6 / 8 | |
| 0.1.0 | 6 / 8 | |
| 0.0.3 | 8 / 9 | |
| 0.0.2 | 8 / 9 | |
| 0.0.1 | 8 / 9 |
v1.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
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.