@firebase/data-connect
## Local Development
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Firebase Data Connect was in preview/canary phase; long gap before stable release is expected for this product. Publisher is Google's trusted automation bot. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Version jump from 0.3.x canary to 0.6.0 stable naturally adds many files. New large files are standard ESM build artifacts and source maps for a Firebase SDK module. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; its use as an implicit dependency is expected in TypeScript-compiled Firebase SDK packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Short README and no keywords are typical for canary sub-packages in the Firebase JS SDK monorepo; not indicative of spam or malicious intent. | ai |
Versions (showing 100 of 258)
v0.3.10-canary.5200f7bb7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9-canary.ec91a8611
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9-canary.1933324e0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.