@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, so a manually published version cannot be tied back to a reviewed commit.
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 50 of 50)
| 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 | |
| 3.0.33 | 6 / 0 | |
| 3.0.30 | 6 / 0 | |
| 3.0.29 | 6 / 0 | |
| 3.0.28 | 6 / 0 | |
| 3.0.27 | 6 / 0 | |
| 3.0.26 | 6 / 0 | |
| 3.0.25 | 6 / 0 | |
| 3.0.24 | 6 / 0 | |
| 3.0.23 | 6 / 0 | |
| 3.0.22 | 6 / 0 | |
| 3.0.21 | 6 / 0 | |
| 3.0.20 | 6 / 0 | |
| 3.0.19 | 6 / 0 | |
| 3.0.18 | 6 / 0 | |
| 3.0.16 | 6 / 0 | |
| 3.0.15 | 6 / 0 | |
| 3.0.14 | 6 / 0 | |
| 3.0.13 | 6 / 0 | |
| 3.0.12 | 6 / 0 | |
| 3.0.11 | 6 / 0 | |
| 3.0.10 | 6 / 0 | |
| 3.0.9 | 6 / 0 | |
| 3.0.8 | 6 / 0 | |
| 3.0.7 | 6 / 0 | |
| 3.0.6 | 6 / 0 | |
| 3.0.5 | 6 / 0 | |
| 3.0.4 | 6 / 0 | |
| 3.0.3 | 6 / 0 | |
| 3.0.2 | 6 / 0 | |
| 3.0.1 | 6 / 0 |
v3.0.33
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yinlianghui) than the most recent previously approved version (steedos-baozhoutao) on 2026-03-05, but yinlianghui is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.28
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yinlianghui) than the most recent previously approved version (steedos-baozhoutao) on 2026-02-24, but yinlianghui is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.27
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (steedos-baozhoutao) than the most recent previously approved version (yinlianghui) on 2026-02-13, but steedos-baozhoutao is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (steedos-baozhoutao) than the most recent previously approved version (yinlianghui) on 2026-01-28, but steedos-baozhoutao is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.21
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yinlianghui) than the most recent previously approved version (steedos-baozhoutao) on 2026-01-23, but yinlianghui is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.20
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yinlianghui) than the most recent previously approved version (steedos-baozhoutao) on 2026-01-22, but yinlianghui is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yinlianghui) than the most recent previously approved version (steedos-baozhoutao) on 2026-01-20, but yinlianghui is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.16
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (steedos-baozhoutao) than the most recent previously approved version (yinlianghui) on 2026-01-16, but steedos-baozhoutao is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yinlianghui) than the most recent previously approved version (lizhengsteedos) on 2026-01-13, but yinlianghui is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yinlianghui) than the most recent previously approved version (lizhengsteedos) on 2026-01-09, but yinlianghui is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lizhengsteedos) than the most recent previously approved version (steedos-baozhoutao) on 2026-01-06, but lizhengsteedos is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lizhengsteedos) than the most recent previously approved version (steedos-baozhoutao) on 2025-12-31, but lizhengsteedos is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (steedos-baozhoutao) than the most recent previously approved version (steedos-sunhaolin) on 2025-12-18, but steedos-baozhoutao is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yinlianghui) than the most recent previously approved version (steedos-sunhaolin) on 2025-12-18, but yinlianghui is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (steedos-sunhaolin) than the most recent previously approved version (steedos-baozhoutao) on 2025-12-16, but steedos-sunhaolin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (steedos-zhuangjianguo) than the most recent previously approved version (steedos-baozhoutao) on 2025-12-11, but steedos-zhuangjianguo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.