← Home

@firebase/app-check-compat

npm Repository Homepage

A compat App Check package for new firebase packages

100
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
dependencies unvetted-dep:@firebase/util AI (dependencies): @firebase/util is a first-party Firebase package from the same Google/Firebase org; not a third-party risk for this package. ai
provenance publisher-changed AI (provenance): Publisher change from feiyang.chen to chholland is a documented Firebase team transition in Jan 2022, consistent across many Firebase packages. chholland is a long-standing Firebase publisher. ai
bogus-package bogus-package AI (bogus-package): Firebase SDK sub-packages intentionally have minimal READMEs and no keywords; this is a stable pattern across all Firebase npm packages, not a spam indicator. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a standard TypeScript runtime helper bundled via rollup in Firebase SDK packages; phantom detection is a false positive for this monorepo build pattern. ai
phantom-deps phantom-dep:@firebase/logger AI (phantom-deps): Same-org Firebase sibling package; phantom detection is a false positive for this monorepo build pattern. ai

Versions (showing 100 of 284)

Hide prereleases
Version Deps Published
0.4.4 6 / 7
0.4.3 6 / 7
0.4.2 6 / 7
0.4.1 6 / 7
0.4.0 6 / 7
0.3.26 6 / 7
0.3.25 6 / 7
0.3.24 6 / 7
0.3.23 6 / 7
0.3.22 6 / 7
0.3.21 6 / 7
0.3.20 6 / 7
0.3.19 6 / 7
0.3.18 6 / 7
0.3.17 6 / 7
0.3.16 6 / 7
0.3.15 6 / 7
0.3.14 6 / 7
0.3.13 6 / 7
0.3.12 6 / 7
0.3.11 6 / 7
0.3.10 6 / 7
0.3.9 6 / 7
0.3.8 6 / 7
0.3.7 6 / 7
0.3.6 6 / 7
0.3.5 6 / 7
0.3.4 6 / 7
0.3.3 6 / 7
0.3.2 6 / 7
0.3.1 6 / 7
0.3.0 6 / 7
0.2.17 6 / 7
0.2.16 6 / 7
0.2.15 6 / 7
0.2.14 6 / 7
0.2.13 6 / 7
0.2.12 6 / 7
0.2.11 6 / 7
0.2.10 6 / 7
0.2.9 6 / 7
0.2.8 6 / 7
0.2.7 6 / 7
0.2.6 6 / 7
0.2.5 6 / 7
0.2.4 5 / 7
0.2.3 5 / 7
0.2.2 5 / 7
0.2.1 5 / 7
0.2.0 5 / 7
0.1.3 5 / 7
0.1.2 5 / 7
0.1.1 5 / 7
0.1.0 5 / 7
0.4.2-canary.f4e0086e3 6 / 7
0.4.2-canary.bfb9accdc 6 / 7
0.4.2-canary.ba0bc39bb 6 / 7
0.4.2-canary.742e17a8e 6 / 7
0.4.2-canary.44ad4cc2e 6 / 7
0.4.2-20260317152345 6 / 7
0.4.1-canary.d7b182645 6 / 7
0.4.1-canary.891a0c9d4 6 / 7
0.4.1-canary.843a8d789 6 / 7
0.4.1-canary.792c61671 6 / 7
0.4.1-canary.78384d32c 6 / 7
0.4.1-canary.22476e1bc 6 / 7
0.4.1-20260224183151 6 / 7
0.4.0-firebase-studio-sdk-integration.f7536090e 6 / 7
0.4.0-firebase-studio-sdk-integration.556d1bed2 6 / 7
0.4.0-eap-firestore-pipelines.2.e4cdd2e06 6 / 7
0.4.0-eap-firestore-pipelines.1.f9c4cdec7 6 / 7
0.4.0-canary.f9aaeca46 6 / 7
0.4.0-canary.f9254b6d2 6 / 7
0.4.0-canary.f5fc6bf76 6 / 7
0.4.0-canary.f2ecae7df 6 / 7
0.4.0-canary.f0b0398eb 6 / 7
0.4.0-canary.f06cbf99b 6 / 7
0.4.0-canary.efc0117ae 6 / 7
0.4.0-canary.ea8512812 6 / 7
0.4.0-canary.e6415ddee 6 / 7
0.4.0-canary.e4b2890fd 6 / 7
0.4.0-canary.e25317f9f 6 / 7
0.4.0-canary.d818df4e8 6 / 7
0.4.0-canary.d7c311a4b 6 / 7
0.4.0-canary.d5ff5a4b1 6 / 7
0.4.0-canary.d4b22a872 6 / 7
0.4.0-canary.d1d898f55 6 / 7
0.4.0-canary.ccbf7ba36 6 / 7
0.4.0-canary.cc605e728 6 / 7
0.4.0-canary.cbef6c6e5 6 / 7
0.4.0-canary.cb3bdd812 6 / 7
0.4.0-canary.c8263c471 6 / 7
0.4.0-canary.c5f08a9bc 6 / 7
0.4.0-canary.c4a3a5643 6 / 7
0.4.0-canary.c48b47674 6 / 7
0.4.0-canary.c47bd7175 6 / 7
0.4.0-canary.c1237662e 6 / 7
0.4.0-canary.bc5a7c4a7 6 / 7
0.4.0-canary.bc2b2cdea 6 / 7
0.4.0-canary.b9209dc91 6 / 7
Showing 100 of 284 Next page →

v0.4.4

1 finding
LOW No provenance attestation provenance

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

v0.4.3

1 finding
LOW No provenance attestation provenance

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

v0.4.2-canary.f4e0086e3

1 finding
LOW No provenance attestation provenance

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

v0.4.2-canary.bfb9accdc

1 finding
LOW No provenance attestation provenance

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

v0.4.2-canary.ba0bc39bb

1 finding
LOW No provenance attestation provenance

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

v0.4.2-canary.742e17a8e

1 finding
LOW No provenance attestation provenance

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

v0.4.2-canary.44ad4cc2e

1 finding
LOW No provenance attestation provenance

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

v0.4.2-20260317152345

1 finding
LOW No provenance attestation provenance

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

v0.4.1-canary.d7b182645

1 finding
LOW No provenance attestation provenance

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

v0.4.1-canary.891a0c9d4

1 finding
LOW No provenance attestation provenance

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

v0.4.1-canary.843a8d789

1 finding
LOW No provenance attestation provenance

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

v0.4.1-canary.792c61671

1 finding
LOW No provenance attestation provenance

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

v0.4.1-canary.78384d32c

1 finding
LOW No provenance attestation provenance

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

v0.4.1-canary.22476e1bc

1 finding
LOW No provenance attestation provenance

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

v0.4.1-20260224183151

1 finding
LOW No provenance attestation provenance

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

v0.4.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.

v0.4.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.

v0.4.0-eap-firestore-pipelines.2.e4cdd2e06

1 finding
LOW No provenance attestation provenance

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

v0.4.0-eap-firestore-pipelines.1.f9c4cdec7

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.

v0.4.0-canary.f9aaeca46

1 finding
LOW No provenance attestation provenance

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

v0.4.0-canary.f9254b6d2

1 finding
LOW No provenance attestation provenance

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

v0.4.0-canary.f5fc6bf76

1 finding
LOW No provenance attestation provenance

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

v0.4.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.

v0.4.0-canary.f0b0398eb

1 finding
LOW No provenance attestation provenance

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

v0.4.0-canary.f06cbf99b

1 finding
LOW No provenance attestation provenance

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

v0.4.0-canary.efc0117ae

1 finding
LOW No provenance attestation provenance

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

v0.4.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.

v0.4.0-canary.e6415ddee

1 finding
LOW No provenance attestation provenance

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

v0.4.0-canary.e4b2890fd

1 finding
LOW No provenance attestation provenance

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

v0.4.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.

v0.4.0-canary.d818df4e8

1 finding
LOW No provenance attestation provenance

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

v0.4.0-canary.d7c311a4b

1 finding
LOW No provenance attestation provenance

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

v0.4.0-canary.d5ff5a4b1

1 finding
LOW No provenance attestation provenance

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

v0.4.0-canary.d4b22a872

1 finding
LOW No provenance attestation provenance

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

v0.4.0-canary.d1d898f55

1 finding
LOW No provenance attestation provenance

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

v0.4.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.

v0.4.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.

v0.4.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.

v0.4.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.

v0.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.

v0.4.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.

v0.4.0-canary.c4a3a5643

1 finding
LOW No provenance attestation provenance

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

v0.4.0-canary.c48b47674

1 finding
LOW No provenance attestation provenance

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

v0.4.0-canary.c47bd7175

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.

v0.4.0-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.

v0.4.0-canary.bc5a7c4a7

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.

v0.4.0-canary.bc2b2cdea

1 finding
LOW No provenance attestation provenance

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

v0.4.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.