esformatter — Greenflagged

ECMAScript code beautifier/formatter

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

jzaefferermillermedeiros

Keywords

babelbeautifierbeautifyecmascriptesprimaformatformatterjavascriptjscssourcestylesyntax

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): ruyadorno is a well-established npm publisher with strong track record; transition from millermedeiros appears to be a legitimate maintainer handoff in 2019.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Provenance attestation is a best-practice recommendation; absence is not a security defect for an established package.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): babylon, babel-traverse, and acorn-to-esprima are legitimate AST/parsing packages fully consistent with a JS formatter's functionality. No malicious signal.	ai	2026/04/24
dependencies	unvetted-dep:babel-traverse	AI (dependencies): babel-traverse is a standard Babel ecosystem package; its use in a JS formatter is expected and benign across all versions.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require() in options.js is the intentional plugin/preset loading mechanism for this formatter — user-supplied config paths resolved via the 'resolve' package. Stable false positive for this package.	ai	2026/04/23
phantom-deps	phantom-dep:acorn-to-esprima	AI (phantom-deps): acorn-to-esprima is a declared runtime dependency for parser compatibility; legitimate use in this formatter.	ai	2026/04/23
phantom-deps	phantom-dep:rocambole-node	AI (phantom-deps): rocambole-node is a declared runtime dependency used by the rocambole AST traversal ecosystem this package is built on.	ai	2026/04/23
phantom-deps	phantom-dep:babel-traverse	AI (phantom-deps): babel-traverse is a declared runtime dependency used by esformatter's parser integration; not a phantom dep concern.	ai	2026/04/23

Versions (showing 47 of 47)

Version	Deps	Published
0.11.3	21 / 8	2020-03-17
0.11.1	21 / 8	2019-10-01
0.11.0	21 / 8	2019-10-01
0.10.0	21 / 8	2016-10-30
0.9.6	20 / 6	2016-07-14
0.9.5	20 / 6	2016-06-05
0.9.3	20 / 6	2016-03-28
0.9.2	20 / 6	2016-02-28
0.9.1	20 / 6	2016-02-14
0.9.0	20 / 6	2016-01-29
0.8.2	18 / 6	2016-01-29
0.8.1	18 / 6	2015-10-29
0.8.0	18 / 6	2015-10-29
0.7.3	19 / 6	2015-08-03
0.7.2	19 / 6	2015-07-17
0.7.1	19 / 6	2015-06-26
0.7.0	18 / 6	2015-05-14
0.6.1	14 / 8	2015-03-27
0.6.0	14 / 9	2015-03-26
0.5.1	9 / 8	2015-03-17
0.5.0	9 / 7	2015-02-26
0.4.3	9 / 7	2014-10-13
0.4.2	9 / 7	2014-09-08
0.4.1	9 / 7	2014-07-09
0.4.0	9 / 7	2014-07-06
0.3.2	9 / 7	2014-06-23
0.3.1	10 / 6	2014-06-23
0.3.0	10 / 6	2014-06-20
0.2.0	10 / 6	2014-06-16
0.1.1	9 / 6	2014-05-12
0.1.0	9 / 6	2014-04-16
0.0.16	7 / 6	2014-02-24
0.0.15	6 / 6	2013-12-18
0.0.14	6 / 6	2013-12-18
0.0.13	6 / 6	2013-12-16
0.0.12	6 / 6	2013-12-15
0.0.11	4 / 6	2013-11-07
0.0.10	4 / 5	2013-11-06
0.0.9	3 / 5	2013-11-05
0.0.8	3 / 5	2013-10-30
0.0.7	3 / 5	2013-10-30
0.0.6	3 / 5	2013-08-14
0.0.5	2 / 5	2013-03-18
0.0.4	2 / 5	2013-01-20
0.0.3	2 / 5	2012-12-19
0.0.2	2 / 5	2012-12-14
0.0.1	2 / 3	2012-12-06

v0.11.3

1 finding

LOW No provenance attestation provenance

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

v0.11.1

1 finding

INFO No provenance attestation provenance

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

v0.11.0

2 findings

HIGH Publisher changed: millermedeiros → ruyadorno (on 2019-10-01) provenance

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

v0.10.0

1 finding

INFO No provenance attestation provenance

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

v0.9.6

1 finding

LOW No provenance attestation provenance

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

v0.9.5

1 finding

LOW No provenance attestation provenance

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

v0.9.3

1 finding

LOW No provenance attestation provenance

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

v0.9.2

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

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

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

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

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

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

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.16

1 finding

LOW No provenance attestation provenance

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

v0.0.15

1 finding

LOW No provenance attestation provenance

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

v0.0.14

1 finding

LOW No provenance attestation provenance

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

v0.0.13

1 finding

LOW No provenance attestation provenance

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

v0.0.12

1 finding

LOW No provenance attestation provenance

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

v0.0.11

1 finding

LOW No provenance attestation provenance

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

v0.0.10

1 finding

LOW No provenance attestation provenance

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

v0.0.9

1 finding

LOW No provenance attestation provenance

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

v0.0.8

1 finding

LOW No provenance attestation provenance

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

v0.0.7

1 finding

LOW No provenance attestation provenance

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

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

v0.0.2

1 finding

LOW No provenance attestation provenance

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

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