escodegen-wallaby — Greenflagged

ECMAScript code generator with JSX support

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

artemgovorovsmcenlly

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): artemgovorov (Artem Govorov) is the wallabyjs founder and listed maintainer in package.json; the account transition from smcenlly is a legitimate internal change within the same org.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): The dynamic require in bin/escodegen.js loads the package's own root module via a path derived from __filename — deterministic and not exploitable. Stable false positive for this package.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): escodegen-wallaby is a legitimate, long-lived fork with 25k+ weekly downloads. Short README and missing keywords are cosmetic issues, not spam indicators.	ai	2026/04/23

Versions (showing 45 of 45)

Version	Deps	Published
1.6.45	4 / 9	2025-02-05
1.6.44	4 / 9	2024-05-31
1.6.43	5 / 9	2024-02-16
1.6.42	5 / 9	2023-08-07
1.6.41	5 / 9	2023-05-24
1.6.40	5 / 9	2023-04-03
1.6.39	5 / 9	2023-03-08
1.6.38	5 / 9	2023-03-08
1.6.37	5 / 9	2023-02-08
1.6.36	5 / 9	2023-01-13
1.6.35	5 / 9	2022-06-07
1.6.34	5 / 9	2022-02-10
1.6.33	5 / 9	2021-12-07
1.6.32	5 / 9	2020-11-09
1.6.31	5 / 9	2020-07-08
1.6.30	5 / 9	2020-07-08
1.6.29	5 / 9	2020-07-06
1.6.28	5 / 9	2020-01-10
1.6.27	5 / 9	2019-11-14
1.6.26	5 / 9	2019-09-10
1.6.25	5 / 9	2019-09-09
1.6.24	5 / 9	2019-04-16
1.6.23	5 / 9	2019-02-05
1.6.22	5 / 9	2018-10-31
1.6.21	5 / 9	2018-10-31
1.6.20	5 / 9	2018-09-28
1.6.19	5 / 9	2018-07-13
1.6.18	5 / 9	2018-02-27
1.6.17	5 / 9	2018-01-19
1.6.16	5 / 9	2018-01-03
1.6.15	5 / 9	2017-11-29
1.6.14	5 / 9	2017-11-04
1.6.13	5 / 9	2017-11-04
1.6.12	5 / 9	2017-07-12
1.6.11	5 / 9	2017-04-04
1.6.10	5 / 9	2017-01-31
1.6.9	5 / 9	2017-01-31
1.6.8	5 / 9	2016-12-12
1.6.7	5 / 9	2016-05-18
1.6.6	5 / 9	2016-05-04
1.6.5	5 / 10	2015-05-21
1.6.4	5 / 10	2015-04-28
1.6.3	5 / 10	2015-04-04
1.6.2	5 / 10	2015-03-27
1.6.1	5 / 10	2015-02-16

v1.6.45

1 finding

LOW No provenance attestation provenance

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

v1.6.44

2 findings

HIGH Publisher changed: artemgovorov → smcenlly (on 2024-05-31) provenance

This version was published by a different npm account than previous versions on 2024-05-31. 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.

v1.6.43

1 finding

LOW No provenance attestation provenance

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

v1.6.42

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: smcenlly → artemgovorov (on 2023-08-07) provenance

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

v1.6.41

1 finding

LOW No provenance attestation provenance

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

v1.6.40

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: artemgovorov → smcenlly (on 2023-04-03) provenance

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

v1.6.39

2 findings

HIGH Publisher changed: smcenlly → artemgovorov (on 2023-03-08) provenance

This version was published by a different npm account than previous versions on 2023-03-08. 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.

v1.6.38

2 findings

HIGH Publisher changed: smcenlly → artemgovorov (on 2023-03-08) provenance

This version was published by a different npm account than previous versions on 2023-03-08. 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.

v1.6.37

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: artemgovorov → smcenlly (on 2023-02-08) provenance

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

v1.6.36

1 finding

LOW No provenance attestation provenance

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

v1.6.35

1 finding

LOW No provenance attestation provenance

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

v1.6.34

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: smcenlly → artemgovorov (on 2022-02-10) provenance

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

v1.6.33

1 finding

LOW No provenance attestation provenance

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

v1.6.32

2 findings

HIGH Publisher changed: smcenlly → artemgovorov (on 2020-11-09) provenance

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

v1.6.31

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: artemgovorov → smcenlly (on 2020-07-08) provenance

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

v1.6.30

1 finding

LOW No provenance attestation provenance

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

v1.6.29

1 finding

LOW No provenance attestation provenance

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

v1.6.28

1 finding

LOW No provenance attestation provenance

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

v1.6.27

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: smcenlly → artemgovorov (on 2019-11-14) provenance

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

v1.6.26

2 findings

HIGH Publisher changed: artemgovorov → smcenlly (on 2019-09-10) provenance

This version was published by a different npm account than previous versions on 2019-09-10. 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.

v1.6.25

1 finding

LOW No provenance attestation provenance

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

v1.6.24

1 finding

LOW No provenance attestation provenance

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

v1.6.23

1 finding

LOW No provenance attestation provenance

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

v1.6.22

1 finding

LOW No provenance attestation provenance

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

v1.6.21

1 finding

LOW No provenance attestation provenance

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

v1.6.20

1 finding

LOW No provenance attestation provenance

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

v1.6.19

1 finding

LOW No provenance attestation provenance

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

v1.6.18

1 finding

LOW No provenance attestation provenance

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

v1.6.17

1 finding

LOW No provenance attestation provenance

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

v1.6.16

1 finding

LOW No provenance attestation provenance

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

v1.6.15

1 finding

LOW No provenance attestation provenance

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

v1.6.14

1 finding

LOW No provenance attestation provenance

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

v1.6.13

1 finding

LOW No provenance attestation provenance

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

v1.6.12

1 finding

LOW No provenance attestation provenance

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

v1.6.11

1 finding

LOW No provenance attestation provenance

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

v1.6.10

1 finding

LOW No provenance attestation provenance

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

v1.6.9

1 finding

LOW No provenance attestation provenance

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

v1.6.8

1 finding

LOW No provenance attestation provenance

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

v1.6.7

1 finding

LOW No provenance attestation provenance

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

v1.6.6

1 finding

LOW No provenance attestation provenance

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

v1.6.5

1 finding

LOW No provenance attestation provenance

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

v1.6.4

1 finding

LOW No provenance attestation provenance

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

v1.6.3

1 finding

LOW No provenance attestation provenance

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

v1.6.2

1 finding

LOW No provenance attestation provenance

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

v1.6.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.