eslint-config-fbjs — Greenflagged

For the most part, this configuration matches the ESLint configuration we have internally at Facebook.

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

zpaocpojerfbbradzacher

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): zpao is a well-known Facebook/Meta engineer with a long, trusted npm history (1523 approved packages). The transition from mjesun to zpao is consistent with a legitimate internal Facebook OSS maintainer handoff.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): fb, zpao, and cpojer are well-known Meta/Facebook npm accounts, not spam publishers. False positive from automated spam detection for this legitimate Meta open-source package.	ai	2026/04/23
provenance	no-provenance	AI (provenance): Established Meta package published before Sigstore provenance was standard; absence of attestation is not a risk signal for this package.	ai	2026/04/23

Versions (showing 10 of 10)

Version	Deps	Published
4.0.0	0 / 0	2022-07-11
3.1.1	0 / 0	2019-08-20
3.1.0	0 / 0	2019-03-20
2.1.0	0 / 0	2018-09-20
2.0.1	0 / 0	2017-11-26
2.0.0	0 / 0	2017-07-19
1.1.1	0 / 0	2016-09-14
1.1.0	0 / 0	2016-09-07
1.0.0	0 / 0	2016-07-12
0.0.0	0 / 0	2016-07-11

v4.0.0

2 findings

HIGH Publisher changed: zpao → bradzacher (on 2022-07-11) provenance

This version was published by a different npm account than previous versions on 2022-07-11. 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.

v3.1.1

2 findings

HIGH Publisher changed: mjesun → zpao (on 2019-08-20) provenance

This version was published by a different npm account than previous versions on 2019-08-20. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v3.1.0

2 findings

HIGH Publisher changed: mjesun → zpao (on 2019-03-20) provenance

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

INFO No provenance attestation provenance

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