@mdit/plugin-katex
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/browser-rYOxky-z.js | AI (source-diff): Rollup-bundled KaTeX browser build; minified output is expected for this package's browser export. | ai | |
| source-diff | obfuscated-file:lib/mhchem-DtLscBzB.js | AI (source-diff): Rollup-bundled mhchem plugin; minified output is expected for this package's browser export. | ai | |
| source-diff | obfuscated-file:lib/mhchem-Ca3toNa5.js | AI (source-diff): Minified mhchem chemistry plugin bundle; content is recognizable chemistry-parsing code. | ai | |
| source-diff | obfuscated-file:lib/browser-BWFnmWsV.js | AI (source-diff): Minified KaTeX browser bundle; content is recognizable math-rendering code, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:lib/browser-C67vEnL_.js | AI (source-diff): Minified KaTeX browser bundle; code is legible math-rendering logic, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:lib/mhchem-Dio7AjKK.js | AI (source-diff): Minified mhchem extension for KaTeX; content matches known mhchem chemistry notation parser. | ai | |
| source-diff | obfuscated-file:lib/mhchem-caeoNCyX.js | AI (source-diff): Rollup-bundled mhchem extension for KaTeX; code is recognizable mhchem state-machine logic. | ai | |
| source-diff | obfuscated-file:lib/browser-BwVfrk1j.js | AI (source-diff): Rollup-bundled KaTeX browser build; minified but readable KaTeX/markdown-it logic, no malicious indicators. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase due to bundling KaTeX into browser build; expected for this type of plugin. | ai | |
| phantom-deps | phantom-dep:@mdit/helper | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires because it's a transitive/re-exported dep, not a direct import. | ai | |
| phantom-deps | phantom-dep:@types/markdown-it | AI (phantom-deps): Type-only package loaded by convention; not directly imported in source. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.25.2 | 4 / 0 | |
| 0.25.1 | 4 / 0 | |
| 0.25.0 | 4 / 0 | |
| 0.24.2 | 4 / 0 | |
| 0.24.1 | 4 / 0 | |
| 0.24.0 | 4 / 0 | |
| 0.23.2 | 4 / 0 | |
| 0.23.1 | 4 / 0 | |
| 0.22.0 | 4 / 0 | |
| 0.21.0 | 4 / 0 | |
| 0.20.0 | 4 / 0 | |
| 0.19.0 | 4 / 0 | |
| 0.18.0 | 4 / 0 | |
| 0.17.0 | 4 / 0 |
v0.25.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.