@firecms/data_enhancement
This plugin allows you to enhance data in your [FireCMS](https://firecms.co) project, using ChatGPT.
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/editor | AI (dependencies): Same-org sibling package in the @firecms monorepo; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package; missing metadata is typical for internal sub-packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with other @firecms scoped packages lacking standalone descriptions. | ai | |
| provenance | no-provenance | AI (provenance): FireCMS monorepo packages consistently lack Sigstore attestation; stable false positive for this package family. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 1 / 12 | |
| 3.1.0 | 2 / 12 | |
| 3.0.1 | 2 / 12 | |
| 3.0.0 | 2 / 12 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.