@firecms/collection_editor_firebase
This package provides a hook that allows to build a `CollectionConfigController` that persists data to Firebase Firestore.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@firecms/firebase | AI (dependencies): First-party sibling package within the @firecms org; stable false positive for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; missing description is a consistent pattern across the @firecms org. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the @firecms package family; consistent pattern, not a targeted omission. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established FireCMS monorepo package; missing repo/homepage is a metadata gap, not a spam indicator. | ai |
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.