@crawlee/core
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:stream-chain | AI (phantom-deps): Used for JSON streaming in dataset export; likely dynamically required. | ai | |
| phantom-deps | phantom-dep:@types/tough-cookie | AI (phantom-deps): Type-only dependency, expected to be unimported at runtime. | ai | |
| phantom-deps | phantom-dep:@crawlee/browser-pool | AI (phantom-deps): Same-org monorepo package, used by convention. | ai | |
| dependencies | unvetted-dep:got-scraping | AI (dependencies): Core HTTP scraping dependency maintained by Apify; integral to this package's purpose. | ai | |
| dependencies | unvetted-dep:@apify/consts | AI (dependencies): First-party @apify/* dependency from the same Apify organization. | ai | |
| dependencies | unvetted-dep:@apify/timeout | AI (dependencies): First-party @apify/* dependency from the same Apify organization. | ai | |
| dependencies | unvetted-dep:@crawlee/types | AI (dependencies): Sibling monorepo package from the same Crawlee project. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @crawlee/core is the canonical Apify crawling framework; no relation to the 'cors' package. | ai | |
| dependencies | unvetted-dep:@apify/utilities | AI (dependencies): First-party @apify/* dependency from the same Apify organization. | ai | |
| dependencies | unvetted-dep:@apify/pseudo_url | AI (dependencies): First-party @apify/* dependency from the same Apify organization. | ai | |
| dependencies | unvetted-dep:@apify/datastructures | AI (dependencies): First-party @apify/* dependency from the same Apify organization. | ai | |
| dependencies | unvetted-dep:@crawlee/memory-storage | AI (dependencies): Sibling monorepo package from the same Crawlee project. | ai | |
| dependencies | unvetted-dep:@crawlee/utils | AI (dependencies): Sibling monorepo package from the same Crawlee project. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used for safe error message extraction, not obfuscation; stable pattern in this package. | ai | |
| dependencies | unvetted-dep:@apify/log | AI (dependencies): First-party @apify/* dependency from the same Apify organization; stable across versions. | ai |
Versions (showing 51 of 75)
| Version | Deps | Published |
|---|---|---|
| 3.17.0 | 22 / 0 | |
| 3.16.0 | 22 / 0 | |
| 3.15.3 | 22 / 0 | |
| 3.15.2 | 22 / 0 | |
| 3.15.1 | 22 / 0 | |
| 3.15.0 | 22 / 0 | |
| 3.14.1 | 22 / 0 | |
| 3.14.0 | 22 / 0 | |
| 3.13.10 | 22 / 0 | |
| 3.13.9 | 22 / 0 | |
| 3.13.8 | 22 / 0 | |
| 3.13.7 | 22 / 0 | |
| 3.13.6 | 22 / 0 | |
| 3.13.5 | 22 / 0 | |
| 3.13.4 | 22 / 0 | |
| 3.13.3 | 22 / 0 | |
| 3.13.2 | 22 / 0 | |
| 3.13.1 | 22 / 0 | |
| 3.13.0 | 22 / 0 | |
| 3.12.2 | 22 / 0 | |
| 3.12.1 | 22 / 0 | |
| 3.12.0 | 22 / 0 | |
| 3.11.5 | 22 / 0 | |
| 3.11.4 | 24 / 0 | |
| 3.11.3 | 24 / 0 | |
| 3.11.2 | 24 / 0 | |
| 3.11.1 | 24 / 0 | |
| 3.11.0 | 24 / 0 | |
| 3.10.5 | 24 / 0 | |
| 3.10.4 | 24 / 0 | |
| 3.10.3 | 24 / 0 | |
| 3.10.2 | 24 / 0 | |
| 3.10.1 | 24 / 0 | |
| 3.10.0 | 24 / 0 | |
| 3.9.2 | 24 / 0 | |
| 3.9.1 | 24 / 0 | |
| 3.9.0 | 24 / 0 | |
| 3.8.2 | 24 / 0 | |
| 3.8.1 | 24 / 0 | |
| 3.8.0 | 24 / 0 | |
| 3.7.3 | 24 / 0 | |
| 3.7.2 | 24 / 0 | |
| 3.7.1 | 24 / 0 | |
| 3.7.0 | 24 / 0 | |
| 3.6.2 | 24 / 0 | |
| 3.6.1 | 24 / 0 | |
| 3.6.0 | 24 / 0 | |
| 3.5.8 | 23 / 0 | |
| 3.5.7 | 23 / 0 | |
| 3.5.6 | 23 / 0 | |
| 3.5.5 | 23 / 0 |
v3.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.