@firecms/data_export — Greenflagged

I'll enhance the README with more detailed documentation, configuration options, and better examples:

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

gatti675

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Established @firecms org package; missing metadata is a style issue, not a spam/malware signal.	ai	2026/05/04
phantom-deps	phantom-dep:@firecms/formex	AI (phantom-deps): Same-org sibling dep; phantom detection is a false positive for monorepo packages.	ai	2026/05/04
phantom-deps	phantom-dep:@firecms/schema_inference	AI (phantom-deps): Same-org sibling dep; phantom detection is a false positive for monorepo packages.	ai	2026/05/04

Versions (showing 3 of 3)

Version	Deps	Published
3.2.0	4 / 13	2026-03-31
3.0.1	4 / 13	2026-01-30
3.0.0	4 / 13	2025-12-01

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