@firecms/data_import_export
This plugin is DEPRECATED and will be removed in future versions. Please use the @firecms/data_import and @firecms/data_export packages instead.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@firecms/data_export | AI (dependencies): First-party sibling dep within the @firecms monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@firecms/data_import | AI (dependencies): First-party sibling dep within the @firecms monorepo; stable pattern across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package pattern; missing metadata is consistent across the FireCMS package family. | ai | |
| provenance | no-provenance | AI (provenance): Established FireCMS ecosystem package; provenance absence is consistent across all versions. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 3 / 11 | |
| 3.1.0 | 3 / 11 | |
| 3.0.1 | 3 / 11 | |
| 3.0.0 | 3 / 11 |
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.