@firecms/firebase
This library provides a set of utilities to integrate [FireCMS](https://firecms.co) with [Firebase](https://firebase.google.com/).
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing metadata is a packaging gap, not a spam/malware indicator for this established ecosystem. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with monorepo sub-package publishing pattern for @firecms/* scope. | ai | |
| phantom-deps | phantom-dep:react-router | AI (phantom-deps): Likely re-exported or referenced in config/type files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-router-dom | AI (phantom-deps): Same as react-router; monorepo build artifact pattern. | ai | |
| phantom-deps | phantom-dep:@firecms/data_export | AI (phantom-deps): Same-org sibling; phantom detection is a known false positive in monorepo bundles. | ai | |
| phantom-deps | phantom-dep:@firecms/data_import | AI (phantom-deps): Same-org sibling; phantom detection is a known false positive in monorepo bundles. | ai | |
| phantom-deps | phantom-dep:@firecms/data_enhancement | AI (phantom-deps): Same-org sibling; phantom detection is a known false positive in monorepo bundles. | ai | |
| phantom-deps | phantom-dep:@firecms/schema_inference | AI (phantom-deps): Same-org sibling; phantom detection is a known false positive in monorepo bundles. | ai | |
| phantom-deps | phantom-dep:@firecms/data_import_export | AI (phantom-deps): Same-org sibling; phantom detection is a known false positive in monorepo bundles. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 11 / 8 | |
| 3.1.0 | 11 / 8 | |
| 3.0.1 | 11 / 7 | |
| 3.0.0 | 11 / 7 |
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.