markstream-vue
Streaming-friendly Vue 3 Markdown renderer for docs sites, AI chat UIs, and large documents.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/mhchem.js | AI (source-diff): KaTeX/mhchem chemistry rendering library, minified; consistent with optional katex peer dep. | ai | |
| source-diff | obfuscated-file:dist/index6.js | AI (source-diff): Standard Vite/Rollup minified Vue component bundle; no malicious patterns in code. | ai | |
| source-diff | obfuscated-file:dist/index5.js | AI (source-diff): Standard Vite/Rollup minified bundle output; samples show Vue component code, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/Tooltip.js | AI (source-diff): Minified Vite build output bundling @floating-ui/dom; not obfuscation, stable for this package. | ai | |
| phantom-deps | phantom-dep:@floating-ui/dom | AI (phantom-deps): @floating-ui/dom is a declared runtime dependency bundled into dist; phantom-dep is a false positive here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 4 / 41 | |
| 0.0.13 | 3 / 36 | |
| 0.0.12 | 3 / 36 | |
| 0.0.11 | 3 / 36 | |
| 0.0.10 | 3 / 35 | |
| 0.0.9 | 2 / 33 | |
| 0.0.8 | 2 / 33 | |
| 0.0.6 | 2 / 32 | |
| 0.0.5 | 2 / 32 | |
| 0.0.4 | 2 / 32 | |
| 0.0.3 | 2 / 32 | |
| 0.0.2 | 2 / 32 | |
| 0.0.1 | 1 / 31 |
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
6 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: simon_he.
Newly 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.
Newly 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.0.5
5 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: simon_he.
Newly 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.
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.0.4
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: simon_he.
Newly 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.0.3
2 findingsNewly 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.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.