← Home

@strapi/utils

npm Repository Homepage

Shared utilities for the Strapi packages

51
Versions
SEE LICENSE IN LICENSE
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

pierreburgyaurelsicokoalexandrebodinconvlynico-strapistrapi.adzouzbaronvoninternetmarc-roig-strapijhoward1994bassel17

Keywords

strapiutils

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): alexandrebodin is a long-standing Strapi core maintainer (3230 days, 12955 approved versions). Publisher rotation within the Strapi team is expected. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy is an artifact of comparing v4→v5 major version lines; Strapi 5.x has been actively published. ai
dependencies unvetted-dep:node-machine-id AI (dependencies): node-machine-id is a well-known, stable package legitimately used by Strapi for machine identification (e.g., telemetry). Stable dependency across many Strapi versions. ai
license uncommon-license:SEE LICENSE IN LICENSE AI (license): Strapi uses a custom license file; this SPDX expression is consistent with their known licensing model across all versions. ai

Versions (showing 51 of 55)

View all versions
Version Deps Published
5.47.1 10 / 7
5.47.0 10 / 7
5.46.1 10 / 7
5.46.0 10 / 7
5.45.1 10 / 7
5.45.0 10 / 7
5.44.0 10 / 7
5.43.0 10 / 7
5.42.1 10 / 7
5.35.0 10 / 7
5.34.0 10 / 7
5.33.4 10 / 7
5.33.3 10 / 7
5.33.2 10 / 7
5.33.1 10 / 7
5.33.0 10 / 7
5.32.0 10 / 7
5.31.3 10 / 7
5.31.2 10 / 7
5.31.1 10 / 7
5.31.0 10 / 7
5.30.1 10 / 7
5.30.0 10 / 7
5.29.0 10 / 7
5.28.0 10 / 7
5.27.0 10 / 7
5.26.0 10 / 7
5.25.0 10 / 7
5.24.2 10 / 7
5.24.1 10 / 7
5.24.0 10 / 7
5.23.6 10 / 7
5.23.5 10 / 7
5.23.4 10 / 7
5.23.3 10 / 7
5.23.2 10 / 7
5.23.1 10 / 7
5.23.0 10 / 7
5.22.0 10 / 7
5.21.0 10 / 7
5.20.0 10 / 7
5.19.0 10 / 7
5.18.1 10 / 7
5.18.0 10 / 7
5.17.0 10 / 7
5.16.1 11 / 8
5.16.0 11 / 8
5.15.1 11 / 8
5.15.0 11 / 8
5.14.0 11 / 8
5.13.1 11 / 8

v5.47.1

1 finding
LOW No provenance attestation provenance

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

v5.47.0

1 finding
LOW No provenance attestation provenance

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

v5.46.1

1 finding
LOW No provenance attestation provenance

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

v5.46.0

1 finding
LOW No provenance attestation provenance

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

v5.45.1

1 finding
LOW No provenance attestation provenance

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

v5.45.0

1 finding
LOW No provenance attestation provenance

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

v5.43.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.

v5.42.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.

v5.35.0

1 finding
LOW No provenance attestation provenance

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

v5.34.0

1 finding
LOW No provenance attestation provenance

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

v5.33.4

1 finding
LOW No provenance attestation provenance

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

v5.33.3

1 finding
LOW No provenance attestation provenance

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

v5.33.2

1 finding
LOW No provenance attestation provenance

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

v5.33.1

1 finding
LOW No provenance attestation provenance

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

v5.33.0

1 finding
LOW No provenance attestation provenance

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

v5.32.0

1 finding
LOW No provenance attestation provenance

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

v5.31.3

2 findings
HIGH Publisher changed: bassel17 → alexandrebodin (on 2025-12-03) provenance

This version was published by a different npm account than previous versions on 2025-12-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.31.2

2 findings
HIGH Publisher changed: bassel17 → alexandrebodin (on 2025-11-20) provenance

This version was published by a different npm account than previous versions on 2025-11-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.31.1

2 findings
HIGH Publisher changed: bassel17 → alexandrebodin (on 2025-11-19) provenance

This version was published by a different npm account than previous versions on 2025-11-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.31.0

2 findings
HIGH Publisher changed: bassel17 → alexandrebodin (on 2025-11-12) provenance

This version was published by a different npm account than previous versions on 2025-11-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.30.1

2 findings
HIGH Publisher changed: bassel17 → alexandrebodin (on 2025-11-05) provenance

This version was published by a different npm account than previous versions on 2025-11-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.30.0

2 findings
HIGH Publisher changed: bassel17 → alexandrebodin (on 2025-10-30) provenance

This version was published by a different npm account than previous versions on 2025-10-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.29.0

1 finding
LOW No provenance attestation provenance

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

v5.20.0

1 finding
LOW No provenance attestation provenance

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

v5.16.1

1 finding
LOW No provenance attestation provenance

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

v5.15.0

1 finding
LOW No provenance attestation provenance

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

v5.14.0

1 finding
LOW No provenance attestation provenance

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

v5.13.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.