math-expression-evaluator

A flexible math expression evaluator

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

bugwheels94

Keywords

mathexpressionevaluatorparser

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-takeover	AI (maintainer-change): ankitbug94 → bugwheels94 is the same author (Ankit) migrating npm accounts; transition happened in 2020 with 53 approved packages since.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from ankitbug94 to bugwheels94 occurred in 2020; same person, new account. Stable for this package.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): bugwheels94 is the same author as ankitbug94; legitimate account migration.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Old account ankitbug94 removed as part of legitimate account migration to bugwheels94.	ai	2026/04/24
source-diff	obfuscated-file:dist/es/lexer.js	AI (source-diff): Rollup+terser minified build output for math expression lexer; standard build artifact pattern for this package.	ai	2026/04/24
source-diff	obfuscated-file:dist/es/token.js	AI (source-diff): Rollup+terser minified build output for token definitions; standard build artifact pattern for this package.	ai	2026/04/24

Versions (showing 52 of 52)

Version	Deps	Published
2.0.7	0 / 22	2025-06-06
2.0.6	0 / 22	2024-11-18
2.0.5	0 / 22	2024-02-05
2.0.4	0 / 22	2023-10-22
2.0.3	0 / 22	2023-06-09
2.0.2	0 / 22	2023-01-25
2.0.1	0 / 22	2023-01-22
2.0.0	0 / 22	2022-12-26
1.4.0	0 / 12	2022-07-03
1.3.14	0 / 12	2022-01-29
1.3.13	0 / 12	2022-01-28
1.3.12	1 / 11	2022-01-27
1.3.11	0 / 15	2022-01-26
1.3.10	0 / 15	2022-01-25
1.3.9	0 / 15	2022-01-25
1.3.8	0 / 12	2021-07-02
1.3.7	0 / 12	2020-12-20
1.3.6	0 / 12	2020-12-04
1.3.5	0 / 12	2020-12-04
1.3.4	0 / 12	2020-12-04
1.3.3	0 / 12	2020-11-17
1.3.1	0 / 12	2020-11-16
1.3.0	0 / 12	2020-11-16
1.2.22	0 / 12	2020-01-25
1.2.21	0 / 12	2020-01-25
1.2.20	0 / 12	2020-01-24
1.2.19	0 / 12	2020-01-24
1.2.18	0 / 12	2020-01-24
1.2.17	0 / 5	2017-04-28
1.2.16	0 / 5	2017-02-02
1.2.15	1 / 5	2017-01-20
1.2.14	1 / 5	2016-08-25
1.2.13	1 / 5	2016-08-23
1.2.12	1 / 5	2016-08-22
1.2.11	0 / 5	2016-08-22
1.2.9	0 / 5	2016-06-11
1.2.8	0 / 5	2015-08-10
1.2.7	0 / 5	2015-08-05
1.2.5	0 / 5	2015-08-04
1.2.4	0 / 5	2015-08-02
1.2.3	0 / 5	2015-08-02
1.2.2	0 / 5	2015-08-02
1.2.1	0 / 5	2015-08-01
1.2.0	0 / 5	2015-07-31
1.1.0	0 / 5	2015-07-30
1.0.7	0 / 5	2015-07-21
1.0.6	0 / 5	2015-07-18
1.0.5	0 / 5	2015-07-18
1.0.4	0 / 5	2015-07-18
1.0.3	0 / 5	2015-07-15
1.0.2	0 / 5	2015-07-15
1.0.1	0 / 5	2015-07-15

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

3 findings

HIGH New obfuscated file: dist/es/lexer.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/es/token.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.14

1 finding

LOW No provenance attestation provenance

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

v1.3.13

1 finding

LOW No provenance attestation provenance

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

v1.3.12

1 finding

LOW No provenance attestation provenance

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

v1.3.11

1 finding

LOW No provenance attestation provenance

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

v1.3.10

1 finding

LOW No provenance attestation provenance

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

v1.3.9

1 finding

LOW No provenance attestation provenance

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

v1.3.8

1 finding

LOW No provenance attestation provenance

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

v1.3.7

1 finding

LOW No provenance attestation provenance

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

v1.3.6

1 finding

LOW No provenance attestation provenance

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

v1.3.5

1 finding

LOW No provenance attestation provenance

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

v1.3.4

1 finding

LOW No provenance attestation provenance

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

v1.3.3

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.22

1 finding

LOW No provenance attestation provenance

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

v1.2.21

1 finding

LOW No provenance attestation provenance

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

v1.2.20

1 finding

LOW No provenance attestation provenance

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

v1.2.19

1 finding

LOW No provenance attestation provenance

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

v1.2.18

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (ankitbug94) were replaced by new maintainers (bugwheels94). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: ankitbug94 → bugwheels94 (on 2020-01-24) provenance

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

1 finding

LOW No provenance attestation provenance

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

v1.2.16

1 finding

LOW No provenance attestation provenance

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

v1.2.15

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: ankit31894 → ankitbug94 (on 2017-01-20) provenance

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

v1.2.14

1 finding

LOW No provenance attestation provenance

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

v1.2.13

1 finding

LOW No provenance attestation provenance

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

v1.2.12

1 finding

LOW No provenance attestation provenance

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

v1.2.11

1 finding

LOW No provenance attestation provenance

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

v1.2.9

1 finding

LOW No provenance attestation provenance

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

v1.2.8

1 finding

LOW No provenance attestation provenance

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

v1.2.7

1 finding

LOW No provenance attestation provenance

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

v1.2.5

1 finding

LOW No provenance attestation provenance

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

v1.2.4

1 finding

LOW No provenance attestation provenance

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

v1.2.3

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.7

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.2

1 finding

LOW No provenance attestation provenance

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

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