@firebase/remote-config-compat Apache-2.0 42 versions

@firebase/remote-config-compat

npm Repository Homepage

The compatibility package of Remote Config

42

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.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@firebase/util	AI (dependencies): First-party Firebase package from the same Google/Firebase org; stable dependency across all Firebase SDK releases.	ai	2026/04/22
dependencies	unvetted-dep:@firebase/remote-config-types	AI (dependencies): First-party Firebase types package from the same Google/Firebase org; stable companion to this package.	ai	2026/04/22
provenance	publisher-changed	AI (provenance): google-wombot is Google/Firebase's official publishing bot account; transition from individual maintainer accounts to this bot is a known, documented Firebase SDK practice.	ai	2026/04/22
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of individual maintainers (hiranya911) is consistent with Firebase SDK consolidating publishing under the google-wombot bot account; not a takeover signal.	ai	2026/04/22
bogus-package	bogus-package	AI (bogus-package): This is a legitimate Firebase SDK compat shim package; short README and no keywords are expected for internal monorepo packages, not spam indicators.	ai	2026/04/22
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a standard TypeScript runtime helper; phantom detection is a false positive for bundled Firebase SDK packages.	ai	2026/04/22
phantom-deps	phantom-dep:@firebase/util	AI (phantom-deps): Same-org Firebase package; phantom detection is a false positive for monorepo bundled output.	ai	2026/04/22
phantom-deps	phantom-dep:@firebase/logger	AI (phantom-deps): Same-org Firebase package; phantom detection is a false positive for monorepo bundled output.	ai	2026/04/22

Versions (showing 42 of 42)

Show 232 prereleases

Version	Deps	Published
0.2.24	6 / 6	2026-05-07
0.2.23	6 / 6	2026-03-19
0.2.22	6 / 6	2026-02-27
0.2.21	6 / 6	2026-01-14
0.2.20	6 / 6	2025-09-18
0.2.19	6 / 6	2025-07-17
0.2.18	6 / 6	2025-06-30
0.2.17	6 / 6	2025-05-20
0.2.16	6 / 6	2025-05-14
0.2.15	6 / 6	2025-05-14
0.2.14	6 / 6	2025-05-07
0.2.13	6 / 6	2025-02-27
0.2.12	6 / 6	2025-01-16
0.2.11	6 / 6	2024-11-14
0.2.10	6 / 6	2024-10-21
0.2.9	6 / 6	2024-09-18
0.2.8	6 / 6	2024-07-03
0.2.7	6 / 6	2024-05-13
0.2.6	6 / 6	2024-03-28
0.2.5	6 / 6	2024-02-01
0.2.4	6 / 6	2023-03-02
0.2.3	6 / 6	2023-02-03
0.2.2	6 / 6	2023-02-02
0.2.1	6 / 6	2023-01-19
0.2.0	6 / 6	2022-12-08
0.1.16	6 / 6	2022-10-27
0.1.15	6 / 6	2022-10-12
0.1.14	6 / 6	2022-10-11
0.1.13	6 / 6	2022-10-06
0.1.12	6 / 6	2022-07-07
0.1.11	6 / 6	2022-06-23
0.1.10	6 / 6	2022-06-09
0.1.9	6 / 6	2022-05-06
0.1.8	6 / 6	2022-04-14
0.1.7	6 / 6	2022-03-24
0.1.6	6 / 6	2022-03-17
0.1.5	6 / 6	2022-01-07
0.1.4	6 / 6	2021-11-08
0.1.3	6 / 6	2021-11-04
0.1.2	6 / 6	2021-10-14
0.1.1	6 / 6	2021-09-24
0.1.0	6 / 6	2021-08-25

v0.2.24

1 finding

LOW No provenance attestation provenance

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

v0.2.23

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

1 finding

LOW No provenance attestation provenance

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

v0.2.21

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

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

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

1 finding

LOW No provenance attestation provenance

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

v0.2.17

1 finding

LOW No provenance attestation provenance

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

v0.2.16

1 finding

LOW No provenance attestation provenance

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

v0.2.15

1 finding

LOW No provenance attestation provenance

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

v0.2.14

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

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

1 finding

LOW No provenance attestation provenance

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

v0.2.11

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

1 finding

LOW No provenance attestation provenance

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

v0.2.9

1 finding

LOW No provenance attestation provenance

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

v0.2.8

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

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

2 findings

HIGH Publisher changed: feiyang.chen → google-wombot (on 2024-03-28) provenance

This version was published by a different npm account than previous versions on 2024-03-28. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.2.5

1 finding

LOW No provenance attestation provenance

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

v0.2.4

2 findings

HIGH Publisher changed: feiyang.chen → google-wombot (on 2023-03-02) provenance

This version was published by a different npm account than previous versions on 2023-03-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.16

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → google-wombot (on 2022-10-27) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-10-27. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.15

1 finding

LOW No provenance attestation provenance

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

v0.1.14

1 finding

LOW No provenance attestation provenance

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

v0.1.13

1 finding

LOW No provenance attestation provenance

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

v0.1.12

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → google-wombot (on 2022-07-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-07. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.11

1 finding

LOW No provenance attestation provenance

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

v0.1.10

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → google-wombot (on 2022-06-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-09. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.9

1 finding

LOW No provenance attestation provenance

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

v0.1.8

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → chholland (on 2022-04-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-14. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → chholland (on 2022-01-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-01-07. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2021-11-04) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-11-04. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → chholland (on 2021-10-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-10-14. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.1

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

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.