@mulmoclaude/html-plugin
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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/dispatch-CdJpUoo-.cjs | AI (source-diff): Vite-bundled build output, not true obfuscation; matches package's own vue build. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Expected from adding built dist/vue subpath output. | ai | |
| source-diff | obfuscated-file:dist/dispatch-BODL3dOR.cjs | AI (source-diff): Bundled vite build output, not obfuscation; content is tool schema/i18n strings. | ai | |
| source-diff | obfuscated-file:dist/vue.cjs | AI (source-diff): Bundled vite build output for Vue view, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/dispatch-DQ4MZCXo.cjs | AI (source-diff): Vite-bundled minified output, not obfuscation; content is readable tool schema strings. | ai | |
| phantom-deps | phantom-dep:@mulmoclaude/common | AI (phantom-deps): Same-org scope, likely used transitively via build. | ai | |
| dependencies | unvetted-dep:@mulmoclaude/core | AI (dependencies): Same-org sibling package, part of monorepo split. | ai | |
| source-diff | obfuscated-file:dist/dispatch-D-Ikq-Dp.cjs | AI (source-diff): Bundled/minified vite output, not obfuscation; no malicious behavior in sample. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.2 | 2 / 19 | |
| 1.0.1 | 2 / 19 | |
| 1.0.0 | 0 / 17 | |
| 0.2.5 | 0 / 17 | |
| 0.2.4 | 0 / 17 | |
| 0.2.2 | 0 / 17 | |
| 0.2.1 | 0 / 17 | |
| 0.2.0 | 0 / 17 | |
| 0.1.0 | 0 / 6 |
v1.0.2
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.
v1.0.1
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.
v1.0.0
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.2.5
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.