@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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Attested CI publish; monorepo tooling likely omits gitHead, no behavior change. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived monorepo package resuming release cadence, not an isolated account signal. | 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/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/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/mhchem-Ca3toNa5.js | AI (source-diff): Minified mhchem chemistry plugin bundle; content is recognizable chemistry-parsing code. | 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 | source-size-tripled | AI (source-diff): Size increase due to bundling KaTeX into browser build; expected for this type of plugin. | 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 | obfuscated-file:lib/mhchem-caeoNCyX.js | AI (source-diff): Rollup-bundled mhchem extension for KaTeX; code is recognizable mhchem state-machine logic. | 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 65 of 65)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 4 / 0 | |
| 1.0.0 | 4 / 0 | |
| 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 | |
| 0.16.7 | 4 / 0 | |
| 0.16.6 | 4 / 0 | |
| 0.16.2 | 4 / 0 | |
| 0.16.1 | 4 / 0 | |
| 0.16.0 | 4 / 0 | |
| 0.15.1 | 4 / 0 | |
| 0.15.0 | 4 / 0 | |
| 0.14.0 | 5 / 0 | |
| 0.13.1 | 4 / 0 | |
| 0.13.0 | 4 / 0 | |
| 0.12.0 | 4 / 0 | |
| 0.11.0 | 4 / 0 | |
| 0.10.1 | 4 / 0 | |
| 0.10.0 | 4 / 0 | |
| 0.9.0 | 3 / 1 | |
| 0.8.0 | 3 / 1 | |
| 0.7.7 | 3 / 1 | |
| 0.7.6 | 3 / 1 | |
| 0.7.5 | 3 / 1 | |
| 0.7.4 | 3 / 1 | |
| 0.7.3 | 3 / 1 | |
| 0.7.2 | 3 / 1 | |
| 0.7.1 | 3 / 1 | |
| 0.7.0 | 3 / 1 | |
| 0.6.5 | 3 / 1 | |
| 0.6.4 | 3 / 1 | |
| 0.6.3 | 3 / 1 | |
| 0.6.2 | 3 / 1 | |
| 0.6.1 | 3 / 1 | |
| 0.6.0 | 3 / 1 | |
| 0.5.2 | 3 / 1 | |
| 0.5.1 | 3 / 1 | |
| 0.5.0 | 3 / 0 | |
| 0.4.8 | 5 / 0 | |
| 0.4.7 | 5 / 0 | |
| 0.4.6 | 5 / 0 | |
| 0.4.5 | 5 / 0 | |
| 0.4.4 | 5 / 0 | |
| 0.4.3 | 5 / 0 | |
| 0.4.2 | 5 / 0 | |
| 0.4.1 | 5 / 0 | |
| 0.4.0 | 5 / 0 | |
| 0.3.0 | 5 / 0 | |
| 0.2.4 | 5 / 0 | |
| 0.2.3 | 5 / 0 | |
| 0.2.2 | 5 / 0 | |
| 0.2.1 | 5 / 0 | |
| 0.2.0 | 5 / 0 | |
| 0.1.0 | 5 / 0 |
v1.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.