katex MIT 47 versions

katex

npm Repository Homepage

Fast math typesetting for the web.

47

Versions

MIT

License

No

Install Scripts

Missing

Provenance

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

xymostechgagernkevinbarabashedemainekhanacademysophiebitsylemkimon

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): commander is a well-established CLI library added to support KaTeX's CLI binary (cli.js). Legitimate and expected for this package.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): edemaine (Erik Demaine, MIT professor) is a known KaTeX contributor. Addition is a legitimate project maintainer expansion.	ai	2026/04/24
typosquat	typosquat.levenshtein:knex	AI (typosquat): KaTeX is a well-established math rendering library (Khan Academy); the name derives from K+TeX, not a typosquat of 'knex'. This is a stable false positive for this package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): edemaine (Erik Demaine) is a known long-standing KaTeX maintainer/contributor with 101 approved packages; this is a legitimate maintainer transition for the KaTeX project.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): KaTeX is a well-established library; short npm README and missing keywords are cosmetic issues, not spam indicators, for this mature package.	ai	2026/04/23

Versions (showing 47 of 47)

Version	Deps	Published
0.17.0	1 / 75	2026-05-22
0.16.47	1 / 75	2026-05-16
0.16.46	1 / 76	2026-05-13
0.16.45	1 / 76	2026-04-05
0.16.44	1 / 76	2026-03-27
0.16.43	1 / 76	2026-03-26
0.16.42	1 / 76	2026-03-24
0.16.41	1 / 76	2026-03-24
0.16.40	1 / 76	2026-03-20
0.16.39	1 / 76	2026-03-19
0.16.38	1 / 76	2026-03-08
0.16.37	1 / 76	2026-03-06
0.16.36	1 / 76	2026-03-06
0.16.35	1 / 77	2026-03-05
0.16.34	1 / 77	2026-03-05
0.16.33	1 / 74	2026-02-23
0.16.32	1 / 74	2026-02-22
0.16.31	1 / 74	2026-02-22
0.16.30	1 / 74	2026-02-22
0.16.29	1 / 74	2026-02-22
0.16.28	1 / 75	2026-01-25
0.16.27	1 / 75	2025-12-07
0.16.26	1 / 75	2025-12-07
0.16.25	1 / 75	2025-10-13
0.16.24	1 / 74	2025-10-12
0.16.23	1 / 74	2025-10-03
0.16.22	1 / 74	2025-04-09
0.16.21	1 / 74	2025-01-17
0.10.2	1 / 54	2019-05-13
0.10.1	1 / 54	2019-02-22
0.10.0	1 / 52	2018-10-29
0.9.0	1 / 37	2018-02-18
0.8.3	1 / 25	2017-08-27
0.8.2	1 / 24	2017-08-17
0.8.1	1 / 23	2017-08-12
0.8.0	1 / 23	2017-08-12
0.7.1	1 / 15	2017-01-21
0.7.0	1 / 14	2017-01-07
0.6.0	1 / 14	2016-04-16
0.5.1	1 / 12	2015-09-02
0.5.0	1 / 9	2015-07-16
0.4.3	1 / 7	2015-06-20
0.4.0	1 / 7	2015-06-18
0.3.0	0 / 7	2015-05-19
0.2.0	0 / 8	2015-03-02
0.1.1	0 / 8	2014-10-16
0.1.0	0 / 7	2014-09-15

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.16.47

1 finding

LOW No provenance attestation provenance

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

v0.16.46

1 finding

LOW No provenance attestation provenance

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

v0.16.45

1 finding

LOW No provenance attestation provenance

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

v0.16.44

1 finding

LOW No provenance attestation provenance

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

v0.16.43

1 finding

LOW No provenance attestation provenance

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

v0.16.42

1 finding

LOW No provenance attestation provenance

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

v0.16.41

1 finding

LOW No provenance attestation provenance

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

v0.16.40

1 finding

LOW No provenance attestation provenance

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

v0.16.39

1 finding

LOW No provenance attestation provenance

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

v0.16.38

1 finding

LOW No provenance attestation provenance

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

v0.16.37

1 finding

LOW No provenance attestation provenance

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

v0.16.36

1 finding

LOW No provenance attestation provenance

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

v0.16.35

1 finding

LOW No provenance attestation provenance

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

v0.16.34

1 finding

LOW No provenance attestation provenance

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

v0.16.33

1 finding

LOW No provenance attestation provenance

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

v0.16.32

1 finding

LOW No provenance attestation provenance

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

v0.16.31

1 finding

LOW No provenance attestation provenance

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

v0.16.30

1 finding

LOW No provenance attestation provenance

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

v0.16.29

1 finding

LOW No provenance attestation provenance

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

v0.16.28

2 findings

HIGH Publisher changed: ylemkimon → edemaine (on 2026-01-25) provenance

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

v0.16.27

1 finding

LOW No provenance attestation provenance

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

v0.16.26

1 finding

LOW No provenance attestation provenance

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

v0.16.25

1 finding

LOW No provenance attestation provenance

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

v0.16.24

1 finding

LOW No provenance attestation provenance

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

v0.16.23

1 finding

LOW No provenance attestation provenance

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

v0.16.22

1 finding

LOW No provenance attestation provenance

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

v0.16.21

1 finding

LOW No provenance attestation provenance

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

v0.10.2

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.

v0.10.1

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ylemkimon.

LOW No provenance attestation provenance

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

INFO Publisher changed: kevinbarabash → ylemkimon (on 2019-02-22) provenance

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

v0.10.0

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.

v0.9.0

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.

v0.8.3

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.

v0.8.2

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.

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

v0.8.0

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.

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

v0.7.0

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.

v0.6.0

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.

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

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: spicyj → xymostech (on 2015-06-18) provenance

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

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

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: spicyj → xymostech (on 2015-03-02) provenance

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

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

v0.1.0

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.