@strapi/data-transfer SEE LICENSE IN LICENSE 49 versions

@strapi/data-transfer

npm Repository Homepage

Data transfer capabilities for Strapi

49

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

strapidatatransferimportexportbackuprestore

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:resolve-cwd	AI (phantom-deps): Declared dependency used in CLI context; phantom-dep pattern is normal for this package type.	ai	2026/04/26
phantom-deps	phantom-dep:inquirer	AI (phantom-deps): Declared dependency used in CLI context; phantom-dep pattern is normal for this package type.	ai	2026/04/26
phantom-deps	phantom-dep:commander	AI (phantom-deps): Declared dependency used in CLI context; phantom-dep pattern is normal for this package type.	ai	2026/04/26
phantom-deps	phantom-dep:cli-table3	AI (phantom-deps): Declared dependency used in CLI context; phantom-dep pattern is normal for this package type.	ai	2026/04/26
phantom-deps	phantom-dep:ora	AI (phantom-deps): Declared dependency used in CLI context; phantom-dep pattern is normal for this package type.	ai	2026/04/26
dependencies	unvetted-dep:@strapi/utils	AI (dependencies): First-party Strapi monorepo package published in lockstep at the same version; not an external unvetted dependency.	ai	2026/04/25
phantom-deps	phantom-dep:@strapi/logger	AI (phantom-deps): Same-org Strapi package; phantom usage is expected in monorepo config files, not a security concern.	ai	2026/04/25
dependencies	unvetted-dep:@strapi/types	AI (dependencies): First-party Strapi monorepo package published in lockstep at the same version; not an external unvetted dependency.	ai	2026/04/25

Versions (showing 49 of 49)

Version	Deps	Published
5.47.1	17 / 15	2026-06-03
5.47.0	17 / 15	2026-05-28
5.46.1	17 / 15	2026-05-20
5.46.0	17 / 15	2026-05-13
5.45.1	17 / 15	2026-05-11
5.45.0	17 / 15	2026-05-06
5.44.0	17 / 15	2026-04-29
5.43.0	17 / 15	2026-04-22
5.42.1	17 / 15	2026-04-15
5.42.0	17 / 15	2026-04-08
5.41.1	17 / 15	2026-04-01
5.41.0	17 / 15	2026-04-01
5.31.3	17 / 16	2025-12-03
5.31.2	17 / 16	2025-11-20
5.31.1	17 / 16	2025-11-19
5.31.0	17 / 16	2025-11-12
5.30.1	17 / 16	2025-11-05
5.30.0	17 / 16	2025-10-30
5.29.0	17 / 16	2025-10-22
5.28.0	17 / 16	2025-10-15
5.27.0	17 / 16	2025-10-08
5.26.0	17 / 16	2025-10-06
5.25.0	17 / 16	2025-10-01
5.24.2	17 / 16	2025-09-29
5.24.1	17 / 16	2025-09-25
5.24.0	17 / 16	2025-09-24
5.23.6	17 / 16	2025-09-19
5.23.5	17 / 16	2025-09-17
5.23.4	17 / 16	2025-09-10
5.23.3	17 / 16	2025-09-04
5.23.2	17 / 16	2025-09-03
5.23.1	17 / 16	2025-08-27
5.23.0	17 / 16	2025-08-20
5.22.0	17 / 16	2025-08-13
5.21.0	17 / 16	2025-08-06
5.20.0	17 / 16	2025-07-30
5.19.0	17 / 16	2025-07-23
5.18.1	17 / 16	2025-07-16
5.18.0	17 / 16	2025-07-09
5.17.0	17 / 16	2025-07-02
5.16.1	17 / 16	2025-06-25
5.16.0	17 / 16	2025-06-17
5.15.1	17 / 16	2025-06-11
5.15.0	17 / 16	2025-06-04
5.14.0	17 / 16	2025-05-28
5.13.1	17 / 16	2025-05-21
5.13.0	17 / 16	2025-05-07
5.12.7	17 / 16	2025-04-30
4.26.0	18 / 16	2025-10-27

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.42.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.41.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.41.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.31.3

1 finding

LOW No provenance attestation provenance

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

v5.31.2

1 finding

LOW No provenance attestation provenance

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

v5.31.1

1 finding

LOW No provenance attestation provenance

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

v5.31.0

1 finding

LOW No provenance attestation provenance

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

v5.30.1

1 finding

LOW No provenance attestation provenance

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

v5.30.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.26.0

1 finding

LOW No provenance attestation provenance

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

v5.23.5

1 finding

LOW No provenance attestation provenance

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

v5.15.1

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. Consider requesting the maintainer enable provenance via CI/CD.

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

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.

v4.26.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.