@crawlee/utils No license 74 versions

@crawlee/utils

npm Repository Homepage

74

Versions

—

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

mtrunkatjancurnpetrpatekmnmkngjaroslavhejlekdrobnikjmetalwarrior665fnesvedab4nanjanbucharapify-service-account

Keywords

apifycrawlerscrawlingutilitiesutils

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@types/sax	AI (phantom-deps): @types/sax is a type declaration package for sax, which is a direct runtime dep; phantom-dep false positive for this package.	ai	2026/04/28

Versions (showing 74 of 74)

Version	Deps	Published
3.17.0	12 / 1	2026-06-04
3.16.0	12 / 1	2026-02-06
3.15.3	12 / 1	2025-11-10
3.15.2	12 / 1	2025-10-23
3.15.1	12 / 1	2025-09-26
3.15.0	12 / 1	2025-09-17
3.14.1	12 / 1	2025-08-05
3.14.0	12 / 1	2025-07-25
3.13.10	12 / 1	2025-07-09
3.13.9	12 / 1	2025-06-27
3.13.8	12 / 1	2025-06-16
3.13.7	12 / 1	2025-06-06
3.13.6	12 / 1	2025-06-05
3.13.5	12 / 1	2025-05-20
3.13.4	12 / 1	2025-05-14
3.13.3	12 / 1	2025-05-05
3.13.2	12 / 1	2025-04-08
3.13.1	12 / 1	2025-04-07
3.13.0	12 / 1	2025-03-04
3.12.2	12 / 1	2025-01-27
3.12.1	12 / 1	2024-12-04
3.12.0	12 / 1	2024-11-04
3.11.5	12 / 1	2024-10-04
3.11.4	12 / 1	2024-09-23
3.11.3	12 / 1	2024-09-03
3.11.2	12 / 1	2024-08-28
3.11.1	12 / 1	2024-07-24
3.11.0	12 / 1	2024-07-09
3.10.5	12 / 1	2024-06-12
3.10.4	12 / 1	2024-06-11
3.10.3	12 / 1	2024-06-07
3.10.2	12 / 1	2024-06-03
3.10.1	11 / 1	2024-05-23
3.10.0	11 / 1	2024-05-16
3.9.2	10 / 0	2024-04-17
3.9.1	10 / 0	2024-04-11
3.9.0	10 / 0	2024-04-10
3.8.2	10 / 0	2024-03-21
3.8.1	10 / 0	2024-02-22
3.8.0	10 / 0	2024-02-21
3.7.3	10 / 0	2024-01-30
3.7.2	10 / 0	2024-01-09
3.7.1	10 / 0	2024-01-02
3.7.0	9 / 0	2023-12-21
3.6.2	7 / 0	2023-11-26
3.6.1	7 / 0	2023-11-15
3.6.0	7 / 0	2023-11-15
3.5.8	7 / 0	2023-10-17
3.5.7	7 / 0	2023-10-05
3.5.6	7 / 0	2023-10-04
3.5.5	7 / 0	2023-10-02
3.5.4	7 / 0	2023-09-11
3.5.3	7 / 0	2023-08-31
3.5.2	7 / 0	2023-08-21
3.5.1	7 / 0	2023-08-16
3.5.0	7 / 0	2023-07-31
3.4.2	7 / 0	2023-07-19
3.4.1	7 / 0	2023-07-13
3.4.0	7 / 0	2023-06-12
3.3.3	7 / 0	2023-05-31
3.3.2	7 / 0	2023-05-11
3.3.1	7 / 0	2023-04-11
3.3.0	7 / 0	2023-03-09
3.2.2	7 / 0	2023-02-08
3.2.1	7 / 0	2023-02-07
3.2.0	7 / 0	2023-02-07
3.1.2	6 / 0	2022-11-15
3.1.1	6 / 0	2022-11-07
3.1.0	6 / 0	2022-10-13
3.0.4	6 / 0	2022-08-22
3.0.3	6 / 0	2022-08-11
3.0.2	9 / 0	2022-07-28
3.0.1	9 / 0	2022-07-26
3.0.0	9 / 0	2022-07-13

v3.13.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.13.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.11.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.11.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.11.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.11.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.11.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.10.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.10.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.10.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.10.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.10.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.9.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.8.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.8.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.7.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.7.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.6.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.5

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: b4nan → apify-service-account (on 2023-10-02, known maintainer) provenance

This version was published by a different npm account (apify-service-account) than the most recent previously approved version (b4nan) on 2023-10-02, but apify-service-account is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.5.4

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: b4nan → apify-service-account (on 2023-09-11, known maintainer) provenance

This version was published by a different npm account (apify-service-account) than the most recent previously approved version (b4nan) on 2023-09-11, but apify-service-account is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.5.3

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: apify-service-account → b4nan (on 2023-08-31, known maintainer) provenance

This version was published by a different npm account (b4nan) than the most recent previously approved version (apify-service-account) on 2023-08-31, but b4nan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: b4nan → apify-service-account (on 2023-06-12, known maintainer) provenance

This version was published by a different npm account (apify-service-account) than the most recent previously approved version (b4nan) on 2023-06-12, but apify-service-account is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.3.3

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: b4nan → apify-service-account (on 2023-05-31, known maintainer) provenance

This version was published by a different npm account (apify-service-account) than the most recent previously approved version (b4nan) on 2023-05-31, but apify-service-account is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.