crawlee
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:@crawlee/cli | AI (dependencies): First-party monorepo sibling package; always published together at matching versions. | ai | |
| dependencies | unvetted-dep:@crawlee/http | AI (dependencies): First-party monorepo sibling package; always published together at matching versions. | ai | |
| dependencies | unvetted-dep:@crawlee/jsdom | AI (dependencies): First-party monorepo sibling package; always published together at matching versions. | ai | |
| dependencies | unvetted-dep:@crawlee/browser | AI (dependencies): First-party monorepo sibling package; always published together at matching versions. | ai | |
| dependencies | unvetted-dep:@crawlee/cheerio | AI (dependencies): First-party monorepo sibling package; always published together at matching versions. | ai | |
| dependencies | unvetted-dep:@crawlee/linkedom | AI (dependencies): First-party monorepo sibling package; always published together at matching versions. | ai | |
| dependencies | unvetted-dep:@crawlee/puppeteer | AI (dependencies): First-party monorepo sibling package; always published together at matching versions. | ai | |
| dependencies | unvetted-dep:@crawlee/playwright | AI (dependencies): First-party monorepo sibling package; always published together at matching versions. | ai | |
| dependencies | unvetted-dep:@crawlee/browser-pool | AI (dependencies): First-party monorepo sibling package; always published together at matching versions. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 3.17.0 | 14 / 0 | |
| 3.16.0 | 14 / 0 | |
| 3.15.3 | 14 / 0 | |
| 3.15.2 | 14 / 0 | |
| 3.15.1 | 14 / 0 | |
| 3.15.0 | 14 / 0 | |
| 3.14.1 | 14 / 0 | |
| 3.14.0 | 14 / 0 | |
| 3.13.10 | 14 / 0 | |
| 3.13.9 | 14 / 0 | |
| 3.13.8 | 14 / 0 | |
| 3.13.7 | 14 / 0 | |
| 3.13.6 | 14 / 0 | |
| 3.13.5 | 14 / 0 | |
| 3.13.4 | 14 / 0 | |
| 3.13.3 | 14 / 0 |
v3.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.15.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.