@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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @crawlee/core is the canonical Apify crawling framework; no relation to the 'cors' package. | 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 | |
| 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 | |
| dependencies | unvetted-dep:@crawlee/utils | AI (dependencies): Sibling monorepo package from the same Crawlee project. | 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 |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 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 |
v3.16.0
2 findingsPackage name '@crawlee/core' is 1 edit(s) away from popular package 'cors'.
Published 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.