@cowprotocol/sdk-flash-loans
Flash loans for CoW Protocol
Supply chain provenance
Status for the latest visible version.
Maintainers
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): Same-org sibling package from cowprotocol/cow-sdk monorepo; SLSA provenance covers the publish chain. | ai | |
| dependencies | unvetted-dep:@cowprotocol/sdk-config | AI (dependencies): Same-org sibling package from cowprotocol/cow-sdk monorepo; SLSA provenance covers the publish chain. | ai | |
| dependencies | unvetted-dep:@cowprotocol/sdk-trading | AI (dependencies): Same-org sibling package from cowprotocol/cow-sdk monorepo; SLSA provenance covers the publish chain. | ai | |
| dependencies | unvetted-dep:@cowprotocol/sdk-app-data | AI (dependencies): Same-org sibling package from cowprotocol/cow-sdk monorepo; SLSA provenance covers the publish chain. | ai | |
| dependencies | unvetted-dep:@cowprotocol/sdk-order-book | AI (dependencies): Same-org sibling package from cowprotocol/cow-sdk monorepo; SLSA provenance covers the publish chain. | ai | |
| dependencies | unvetted-dep:@cowprotocol/sdk-order-signing | AI (dependencies): Same-org sibling package from cowprotocol/cow-sdk monorepo; SLSA provenance covers the publish chain. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 3.1.1 | 6 / 16 | |
| 3.1.0 | 6 / 16 | |
| 3.0.5 | 6 / 16 | |
| 3.0.4 | 6 / 16 | |
| 3.0.3 | 6 / 16 | |
| 2.0.5 | 6 / 16 | |
| 2.0.2 | 6 / 16 | |
| 2.0.0 | 6 / 16 | |
| 1.7.11 | 6 / 16 | |
| 1.7.10 | 6 / 16 | |
| 1.7.9 | 6 / 16 | |
| 1.7.8 | 6 / 16 | |
| 1.7.7 | 6 / 16 | |
| 1.7.6 | 6 / 16 | |
| 1.7.5 | 6 / 16 | |
| 1.7.4 | 6 / 16 | |
| 1.7.3 | 6 / 16 | |
| 1.7.2 | 6 / 16 | |
| 1.7.1 | 6 / 16 | |
| 1.7.0 | 6 / 16 | |
| 1.6.8 | 6 / 16 | |
| 1.6.7 | 6 / 16 | |
| 1.6.6 | 6 / 16 | |
| 1.6.5 | 6 / 16 | |
| 1.6.4 | 6 / 16 | |
| 1.6.3 | 6 / 16 | |
| 1.6.2 | 6 / 16 | |
| 1.6.1 | 6 / 16 | |
| 1.6.0 | 6 / 16 | |
| 1.5.12 | 6 / 16 | |
| 1.5.11 | 6 / 16 | |
| 1.5.9 | 6 / 16 | |
| 1.5.8 | 6 / 16 | |
| 1.5.7 | 6 / 16 | |
| 1.5.6 | 6 / 16 | |
| 1.5.5 | 6 / 16 | |
| 1.5.4 | 6 / 16 | |
| 1.5.3 | 6 / 16 | |
| 1.5.2 | 6 / 16 | |
| 1.5.0 | 6 / 16 | |
| 1.4.0 | 6 / 16 | |
| 1.3.0 | 6 / 16 | |
| 1.2.1 | 6 / 16 | |
| 1.2.0 | 6 / 16 | |
| 1.1.3 | 6 / 16 |
v3.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.