@storybook/mdx1-csf
MDXv1 to CSF webpack compiler and loader
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Standard esbuild/tsup bundle output with CJS interop helpers; dependencies bundled inline rather than declared as runtime deps. | ai | |
| source-diff | obfuscated-file:dist/index.mjs | AI (source-diff): ESM counterpart of the tsup bundle; same bundled dependencies pattern, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index.js | AI (source-diff): Bundled @babel/parser and code generator contain dynamic patterns triggering heuristics; no actual malicious network/exec code. | ai | |
| source-diff | net-exec-file:dist/index.mjs | AI (source-diff): ESM bundle counterpart; same false positive from bundled babel tooling. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is from bundling previously-external runtime deps (babel, lodash, prettier) into dist output. | ai |
v1.0.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.