babel-preset-fbjs
Babel preset for Facebook projects.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): jstejada is a long-standing Facebook contributor with 518 approved packages and 0 rejected; the publisher change reflects a legitimate maintainer transition within the fbjs project. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jstejada has a strong track record (518 approved/0 rejected, active since 2984 days ago); addition is a legitimate maintainer transition for the fbjs monorepo. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All 27 new deps are official @babel/ scoped packages replacing old babel-plugin-* equivalents — this is the standard Babel 7 migration pattern, not a supply chain attack vector. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.4.0 | 27 / 3 | |
| 3.3.0 | 27 / 3 | |
| 3.2.0 | 27 / 3 | |
| 3.1.2 | 27 / 3 | |
| 3.1.1 | 27 / 3 | |
| 3.1.0 | 27 / 2 | |
| 3.0.1 | 28 / 2 | |
| 3.0.0 | 28 / 2 | |
| 2.3.0 | 28 / 2 | |
| 2.2.0 | 28 / 2 | |
| 2.1.4 | 28 / 2 | |
| 2.1.3 | 28 / 2 | |
| 2.1.2 | 28 / 2 | |
| 2.1.1 | 28 / 2 | |
| 2.1.0 | 28 / 2 | |
| 2.0.0 | 28 / 2 | |
| 1.0.0 | 24 / 2 |
v3.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-10-11. This could indicate a legitimate maintainer transition or an account compromise.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-07. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-10-22. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2018-09-18. 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.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-07-25. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-06-16. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-06-09. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-05-02. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-04-27. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.