@cowprotocol/cow-sdk
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@cowprotocol/sdk-common | AI (dependencies): First-party monorepo sub-package from cowprotocol org; same publisher and provenance chain. | ai | |
| dependencies | unvetted-dep:@cowprotocol/sdk-config | AI (dependencies): First-party monorepo sub-package from cowprotocol org; same publisher and provenance chain. | ai | |
| dependencies | unvetted-dep:@cowprotocol/sdk-trading | AI (dependencies): First-party monorepo sub-package from cowprotocol org; same publisher and provenance chain. | ai | |
| dependencies | unvetted-dep:@cowprotocol/sdk-app-data | AI (dependencies): First-party monorepo sub-package from cowprotocol org; same publisher and provenance chain. | ai | |
| dependencies | unvetted-dep:@cowprotocol/sdk-order-book | AI (dependencies): First-party monorepo sub-package from cowprotocol org; same publisher and provenance chain. | ai | |
| dependencies | unvetted-dep:@cowprotocol/sdk-contracts-ts | AI (dependencies): First-party monorepo sub-package from cowprotocol org; same publisher and provenance chain. | ai | |
| dependencies | unvetted-dep:@cowprotocol/sdk-order-signing | AI (dependencies): First-party monorepo sub-package from cowprotocol org; same publisher and provenance chain. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 9.1.4 | 7 / 7 | |
| 9.1.3 | 7 / 7 | |
| 9.1.2 | 7 / 7 | |
| 9.1.1 | 7 / 7 | |
| 9.1.0 | 7 / 7 | |
| 8.0.5 | 7 / 7 | |
| 8.0.2 | 7 / 7 | |
| 8.0.0 | 7 / 7 | |
| 7.4.2 | 7 / 7 | |
| 7.4.1 | 7 / 7 | |
| 7.4.0 | 7 / 7 | |
| 7.3.8 | 7 / 7 | |
| 7.3.7 | 7 / 7 | |
| 7.3.6 | 7 / 7 | |
| 7.3.5 | 7 / 7 | |
| 7.3.4 | 7 / 7 | |
| 7.3.3 | 7 / 7 | |
| 7.3.2 | 7 / 7 | |
| 7.3.1 | 7 / 7 | |
| 7.3.0 | 7 / 7 | |
| 7.2.13 | 7 / 7 | |
| 7.2.12 | 7 / 7 | |
| 7.2.11 | 7 / 7 | |
| 7.2.10 | 7 / 7 | |
| 7.2.9 | 7 / 7 | |
| 7.2.8 | 7 / 7 | |
| 7.2.7 | 7 / 7 | |
| 7.2.6 | 7 / 7 | |
| 7.2.5 | 7 / 7 | |
| 7.2.4 | 7 / 7 | |
| 7.2.3 | 7 / 7 | |
| 7.2.2 | 7 / 7 | |
| 7.2.0 | 7 / 7 | |
| 7.1.6 | 7 / 7 | |
| 7.1.5 | 7 / 7 | |
| 7.1.4 | 7 / 7 | |
| 7.1.3 | 7 / 7 | |
| 7.1.2 | 7 / 7 | |
| 7.1.1 | 7 / 7 | |
| 7.1.0 | 7 / 7 |
v9.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.