← Home

@firebase/ai

npm Repository Homepage

The Firebase AI SDK

54
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

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

firebase-opsfeiyang.chengoogle-wombotchholland

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a standard TypeScript runtime helper declared as a direct dependency; phantom-dep false positive for all TypeScript-compiled Firebase packages. ai
bogus-package bogus-package AI (bogus-package): Monorepo sub-package of firebase-js-sdk; short README and no keywords are expected for sub-packages that rely on the parent project's documentation. ai
dependencies unvetted-dep:@firebase/util AI (dependencies): First-party Firebase dependency published by the same Google team; stable false positive for all @firebase/* packages. ai
typosquat typosquat.levenshtein:joi AI (typosquat): @firebase/ai is a scoped Firebase SDK package; Levenshtein distance match against 'joi' is a false positive with no impersonation intent. ai
typosquat typosquat.levenshtein:hapi AI (typosquat): @firebase/ai is a scoped Firebase SDK package; Levenshtein distance match against 'hapi' is a false positive with no impersonation intent. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): @firebase/ai is a scoped Firebase SDK package; Levenshtein distance match against 'ajv' is a false positive with no impersonation intent. ai
typosquat typosquat.levenshtein:pg AI (typosquat): @firebase/ai is a scoped Firebase SDK package; Levenshtein distance match against 'pg' is a false positive with no impersonation intent. ai
typosquat typosquat.levenshtein:qs AI (typosquat): @firebase/ai is a scoped Firebase SDK package; Levenshtein distance match against 'qs' is a false positive with no impersonation intent. ai

Versions (showing 54 of 154)

Hide prereleases
Version Deps Published
2.4.0-canary.c8263c471 5 / 6
2.4.0-canary.bc5a7c4a7 5 / 6
2.4.0-canary.b7e18d0ff 5 / 6
2.4.0-canary.91c218db2 5 / 6
2.4.0-canary.8209266c6 5 / 6
2.4.0-canary.6e0e30317 5 / 6
2.4.0-canary.44d9891f9 5 / 6
2.4.0-canary.261508183 5 / 6
2.4.0-canary.22e0a1adb 5 / 6
2.4.0-20251007135320 5 / 6
2.3.0-canary.ea8512812 5 / 6
2.3.0-canary.ccbf7ba36 5 / 6
2.3.0-canary.cb3bdd812 5 / 6
2.3.0-canary.7a7634f79 5 / 6
2.3.0-canary.2596dd1b5 5 / 6
2.3.0-canary.1bcf83d7f 5 / 6
2.3.0-canary.0ffcb26af 5 / 6
2.3.0-canary.0bb2fe636 5 / 6
2.3.0-caching-fdc.9f17eac6e 5 / 6
2.3.0-20250917161512 5 / 6
2.2.1-canary.c1237662e 5 / 6
2.2.1-canary.a4848b401 5 / 6
2.2.1-canary.9b8ab02c5 5 / 6
2.2.1-canary.6ab71fa0b 5 / 6
2.2.1-canary.55f3f83a7 5 / 6
2.2.1-canary.4d834deb2 5 / 6
2.2.1-canary.43276b041 5 / 6
2.2.1-canary.120a30838 5 / 6
2.2.1-canary.06ab5c4f9 5 / 6
2.2.1-20250829000033 5 / 6
2.2.0-canary.f2ecae7df 5 / 6
2.2.0-canary.095c098de 5 / 6
2.2.0-20250827140758 5 / 6
2.1.0-firebase-studio-sdk-integration.f7536090e 5 / 6
2.1.0-firebase-studio-sdk-integration.556d1bed2 5 / 6
2.1.0-canary.cc605e728 5 / 6
2.1.0-canary.cbef6c6e5 5 / 6
2.1.0-canary.c5f08a9bc 5 / 6
2.1.0-canary.9b63cd60e 5 / 6
2.1.0-canary.984086b0b 5 / 6
2.1.0-canary.84b8bed35 5 / 6
2.1.0-canary.5501791d0 5 / 6
2.1.0-canary.44d8d742f 5 / 6
2.1.0-canary.2058432e6 5 / 6
2.1.0-canary.02280d747 5 / 6
2.1.0-20250806231852 5 / 6
2.0.0-canary.e25317f9f 5 / 6
2.0.0-canary.b9209dc91 5 / 6
2.0.0-canary.a4897a621 5 / 6
2.0.0-canary.56fbe5207 5 / 6
2.0.0-canary.492353771 5 / 6
2.0.0-20250716201504 5 / 6
2.0.0-20250716004940 5 / 6
2.0.0-20250715195345 5 / 6

v2.4.0-canary.c8263c471

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.

v2.4.0-canary.bc5a7c4a7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.0-canary.b7e18d0ff

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.

v2.4.0-canary.91c218db2

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.

v2.4.0-canary.8209266c6

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.

v2.4.0-canary.6e0e30317

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.0-canary.44d9891f9

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.

v2.4.0-canary.261508183

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.

v2.4.0-canary.22e0a1adb

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.

v2.4.0-20251007135320

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.

v2.3.0-canary.ea8512812

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.

v2.3.0-canary.ccbf7ba36

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.

v2.3.0-canary.cb3bdd812

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.

v2.3.0-canary.7a7634f79

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.

v2.3.0-canary.2596dd1b5

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.

v2.3.0-canary.1bcf83d7f

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.

v2.3.0-canary.0ffcb26af

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.

v2.3.0-canary.0bb2fe636

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.

v2.3.0-caching-fdc.9f17eac6e

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.0-20250917161512

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.

v2.2.1-canary.c1237662e

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.

v2.2.1-canary.a4848b401

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.

v2.2.1-canary.9b8ab02c5

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.

v2.2.1-canary.6ab71fa0b

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.

v2.2.1-canary.55f3f83a7

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.

v2.2.1-canary.4d834deb2

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.

v2.2.1-canary.43276b041

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.

v2.2.1-canary.120a30838

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.

v2.2.1-canary.06ab5c4f9

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.

v2.2.1-20250829000033

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.

v2.2.0-canary.f2ecae7df

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.

v2.2.0-canary.095c098de

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.

v2.2.0-20250827140758

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.

v2.1.0-firebase-studio-sdk-integration.f7536090e

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.

v2.1.0-firebase-studio-sdk-integration.556d1bed2

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.

v2.1.0-canary.cc605e728

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.

v2.1.0-canary.cbef6c6e5

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.

v2.1.0-canary.c5f08a9bc

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.

v2.1.0-canary.9b63cd60e

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.

v2.1.0-canary.984086b0b

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.

v2.1.0-canary.84b8bed35

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.

v2.1.0-canary.5501791d0

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.

v2.1.0-canary.44d8d742f

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.

v2.1.0-canary.2058432e6

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.

v2.1.0-canary.02280d747

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.

v2.1.0-20250806231852

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.

v2.0.0-canary.e25317f9f

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.

v2.0.0-canary.b9209dc91

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.

v2.0.0-canary.a4897a621

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.

v2.0.0-canary.56fbe5207

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.

v2.0.0-canary.492353771

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.

v2.0.0-20250716201504

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.

v2.0.0-20250716004940

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.

v2.0.0-20250715195345

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.