@steedos-labs/plugin-workflow
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 | net-exec-file:designer/dist/assets/index-C1lW8aZY.js | AI (source-diff): Bundled frontend code with fetch() and eval() from React/build tooling, not malware. | ai | |
| source-diff | obfuscated-file:designer/dist/assets/index-C1lW8aZY.js | AI (source-diff): Vite-bundled React frontend app; minified dist output, not obfuscation. | ai | |
| source-diff | net-exec-file:designer/dist/assets/index-DpFVuLlI.js | AI (source-diff): Network calls (fetch for modulepreload) and dynamic code in a React SPA bundle are expected; not dropper behavior. | ai | |
| source-diff | obfuscated-file:designer/dist/assets/index-DpFVuLlI.js | AI (source-diff): Standard Vite/React minified bundle; not obfuscated malware. Stable pattern for this package's designer dist output. | ai | |
| source-diff | obfuscated-file:designer/dist/assets/index-5mxwjEK9.js | AI (source-diff): Standard Vite-minified React SPA bundle in designer/dist; not obfuscated malware. | ai | |
| source-diff | net-exec-file:designer/dist/assets/index-5mxwjEK9.js | AI (source-diff): Network calls are modulepreload polyfill fetch; no dynamic code execution beyond normal React rendering. | ai | |
| source-diff | net-exec-file:designer/dist/assets/index-0luPt4e2.js | AI (source-diff): Browser fetch + dynamic module patterns in a bundled SPA; not dropper behavior. | ai | |
| source-diff | obfuscated-file:designer/dist/assets/index-0luPt4e2.js | AI (source-diff): Standard Vite/React minified bundle for the designer UI; not obfuscated malware. | ai | |
| source-diff | net-exec-file:designer/dist/assets/index-WAa42ctb.js | AI (source-diff): Network calls (fetch for modulepreload) and dynamic code in a React bundle are normal; no dropper pattern present. | ai | |
| source-diff | obfuscated-file:designer/dist/assets/index-WAa42ctb.js | AI (source-diff): Standard Vite/React production bundle; minification is expected for this designer dist asset. | ai | |
| source-diff | net-exec-file:designer/dist/assets/index-BfCqQeh8.js | AI (source-diff): Network calls and dynamic code in a React SPA bundle are normal; no dropper pattern present. | ai | |
| source-diff | obfuscated-file:designer/dist/assets/index-BfCqQeh8.js | AI (source-diff): Standard Vite/React minified bundle from documented build:designer step; not obfuscation. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): Workflow condition evaluator pattern; eval on condition_str is expected in rule/formula engines for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Require on a resolved absolute path to read a package.json version; not user-controlled input. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 3.0.85 | 6 / 0 | |
| 3.0.84 | 6 / 0 | |
| 3.0.82 | 6 / 0 | |
| 3.0.81 | 6 / 0 | |
| 3.0.80 | 6 / 0 | |
| 3.0.79 | 6 / 0 | |
| 3.0.78 | 6 / 0 | |
| 3.0.77 | 6 / 0 | |
| 3.0.76 | 6 / 0 | |
| 3.0.75 | 6 / 0 | |
| 3.0.74 | 6 / 0 | |
| 3.0.73 | 6 / 0 | |
| 3.0.72 | 6 / 0 | |
| 3.0.70 | 6 / 0 | |
| 3.0.69 | 6 / 0 | |
| 3.0.68 | 6 / 0 | |
| 3.0.67 | 6 / 0 | |
| 3.0.66 | 6 / 0 | |
| 3.0.65 | 6 / 0 | |
| 3.0.64 | 6 / 0 |
v3.0.85
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 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.
v3.0.84
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 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.
v3.0.82
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 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.
v3.0.81
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 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.
v3.0.80
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 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.
v3.0.79
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 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.
v3.0.78
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 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.
v3.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.76
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 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.
v3.0.75
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 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.
v3.0.74
4 findingsThis version was published by a different npm account than previous versions on 2026-05-11. This could indicate a legitimate maintainer transition or an account compromise.
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.
v3.0.73
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 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.
v3.0.72
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 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.
v3.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.