← Home

mathxyjax3

npm Repository Homepage

MathJax3 with XyJaX-v3 for server side rendering

12
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

taniguchi

Keywords

mathjaxxyjaxxypicsvgmath

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/lib-CBtriEt5.js AI (source-diff): Bundled xmldom/wgxpath output; minification is expected for this MathJax SSR package. ai
source-diff obfuscated-file:dist/liteDOM-Cp0aN3bP.js AI (source-diff): Bundled MathJax liteDOM adapter; minification is expected. ai
source-diff obfuscated-file:dist/tex-svg-full-BI3fonbT.js AI (source-diff): Bundled MathJax tex-svg-full component; minification is expected. ai
source-diff obfuscated-file:dist/wgxpath.install-node-Csk64Aj9.js AI (source-diff): Bundled wicked-good-xpath; minification is expected. ai
source-diff obfuscated-file:dist/xypic-DrMJn58R.js AI (source-diff): Bundled XyJax-v3 component; minification is expected. ai
source-diff net-exec-file:dist/tex-svg-full-BI3fonbT.js AI (source-diff): MathJax uses fetch for font loading and dynamic TeX parsing; not malicious dropper behavior. ai

Versions (showing 12 of 12)

Version Deps Published
0.8.3 0 / 7
0.8.2 0 / 7
0.8.1 0 / 6
0.8.0 0 / 6
0.7.0 0 / 6
0.6.0 0 / 6
0.5.1 0 / 6
0.5.0 0 / 6
0.4.0 0 / 6
0.3.0 0 / 6
0.2.0 0 / 6
0.1.0 0 / 6

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

7 findings
HIGH New obfuscated file: dist/lib-CBtriEt5.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/liteDOM-Cp0aN3bP.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/tex-svg-full-BI3fonbT.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 file with network + code execution: dist/tex-svg-full-BI3fonbT.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New obfuscated file: dist/wgxpath.install-node-Csk64Aj9.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/xypic-DrMJn58R.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.

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