@firebase/app
The primary entrypoint to the Firebase JS SDK
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): Official Firebase SDK sub-package; short README and no keywords are typical for SDK sub-packages that rely on the main firebase package documentation. | ai | |
| provenance | publisher-changed | AI (provenance): google-wombot is Google's official Firebase publishing bot; transition from firebase-ops to google-wombot is a documented infrastructure change across all Firebase packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Firebase/Google team members; google-wombot is Google's automated publishing account. Legitimate team transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are former Firebase team members. Combined with addition of google-wombot, this reflects a legitimate organizational transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is an artifact of comparing against a very old canary version; the package has 3716 versions and has been actively maintained throughout. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): @firebase/app is the official Firebase JS SDK; levenshtein match against 'hapi' is a false positive for this scoped package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @firebase/app is the official Firebase JS SDK; levenshtein match against 'pg' is a false positive for this scoped package. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @firebase/app is the official Firebase JS SDK; levenshtein match against 'yup' is a false positive for this scoped package. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): @firebase/app is the official Firebase JS SDK; levenshtein match against 'ajv' is a false positive for this scoped package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; implicit usage in compiled TS packages is expected and stable for this package. | ai |
Versions (showing 51 of 208)
| Version | Deps | Published |
|---|---|---|
| 0.14.12 | 5 / 6 | |
| 0.14.11 | 5 / 6 | |
| 0.14.10 | 5 / 6 | |
| 0.14.9 | 5 / 6 | |
| 0.14.8 | 5 / 6 | |
| 0.14.7 | 5 / 6 | |
| 0.14.6 | 5 / 6 | |
| 0.14.5 | 5 / 6 | |
| 0.14.4 | 5 / 6 | |
| 0.14.3 | 5 / 6 | |
| 0.14.2 | 5 / 6 | |
| 0.14.1 | 5 / 6 | |
| 0.14.0 | 5 / 6 | |
| 0.13.2 | 5 / 6 | |
| 0.13.1 | 5 / 6 | |
| 0.13.0 | 5 / 6 | |
| 0.12.3 | 5 / 6 | |
| 0.12.2 | 5 / 6 | |
| 0.12.1 | 5 / 6 | |
| 0.12.0 | 5 / 6 | |
| 0.11.5 | 5 / 6 | |
| 0.11.4 | 5 / 6 | |
| 0.11.3 | 5 / 6 | |
| 0.11.2 | 5 / 6 | |
| 0.11.1 | 5 / 6 | |
| 0.11.0 | 5 / 6 | |
| 0.10.18 | 5 / 6 | |
| 0.10.17 | 5 / 6 | |
| 0.10.16 | 5 / 6 | |
| 0.10.15 | 5 / 6 | |
| 0.10.14 | 5 / 6 | |
| 0.10.13 | 5 / 6 | |
| 0.10.12 | 5 / 6 | |
| 0.10.11 | 5 / 6 | |
| 0.10.10 | 5 / 6 | |
| 0.10.9 | 5 / 6 | |
| 0.10.8 | 5 / 6 | |
| 0.10.7 | 5 / 6 | |
| 0.10.6 | 5 / 6 | |
| 0.10.5 | 5 / 6 | |
| 0.10.4 | 5 / 6 | |
| 0.10.3 | 5 / 6 | |
| 0.10.2 | 5 / 6 | |
| 0.10.1 | 5 / 6 | |
| 0.10.0 | 5 / 6 | |
| 0.9.29 | 5 / 6 | |
| 0.9.28 | 5 / 6 | |
| 0.9.27 | 5 / 6 | |
| 0.9.26 | 5 / 6 | |
| 0.9.25 | 5 / 6 | |
| 0.9.24 | 5 / 6 |
v0.14.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.11
2 findingsThis version was published by a different npm account than previous versions on 2026-04-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.