← Home

@steedos/service-workflow

npm

<!-- * @Author: [email protected] * @Date: 2021-10-27 15:58:16 * @LastEditors: [email protected] * @LastEditTime: 2023-03-30 15:26:58 * @Description: --> ## 功能说明 - 审批王服务，包含 流程触发器

13
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

steedos-zhuangjianguosteedos-baozhoutaochenzhipeiyinlianghuisteedos-sunhaolin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Loads a resolved local package.json path, not arbitrary user input. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): Flagged text is inside a comment, not an actual HTTP request. ai
semgrep semgrep:eval-usage AI (semgrep): eval used for runtime formula evaluation, consistent with workflow engine pattern across all versions. ai
phantom-deps phantom-dep:node-schedule AI (phantom-deps): node-schedule is declared in dependencies; phantom-dep heuristic false positive for this package. ai

Versions (showing 13 of 13)

Version Deps Published
2.7.32 5 / 0
2.7.31 5 / 0
2.7.30 5 / 0
2.7.29 5 / 0
2.7.28 5 / 0
2.7.27 5 / 0
2.7.25 5 / 0
2.7.24 5 / 0
2.7.22 5 / 0
2.7.21 5 / 0
2.7.20 5 / 0
2.7.19 5 / 0
2.7.18 5 / 0

v2.7.32

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.31

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.30

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.29

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.28

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.7.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.7.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.7.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.