@nocobase/flow-engine
A standalone flow engine for NocoBase, managing workflows, models, and actions.
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 |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is used in flowI18n.js for template option parsing, wrapped in try/catch. Standard i18n template engine pattern for this type of package. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() is used in Proxy handler for BlockScopedFlowEngine scoped variable lookup — standard JS pattern for flow engines, not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of the @nocobase monorepo ecosystem with 173 versions and real downloads; sparse README is a monorepo artifact, not a spam/phishing indicator. | ai |
Versions (showing 51 of 91)
| Version | Deps | Published |
|---|---|---|
| 2.1.30 | 16 / 1 | |
| 2.1.29 | 16 / 1 | |
| 2.1.28 | 16 / 1 | |
| 2.1.27 | 16 / 1 | |
| 2.1.26 | 16 / 1 | |
| 2.1.25 | 16 / 1 | |
| 2.1.24 | 16 / 1 | |
| 2.1.23 | 16 / 1 | |
| 2.1.22 | 16 / 1 | |
| 2.1.21 | 16 / 1 | |
| 2.1.20 | 16 / 1 | |
| 2.1.19 | 16 / 1 | |
| 2.1.18 | 16 / 1 | |
| 2.1.17 | 16 / 1 | |
| 2.1.15 | 16 / 1 | |
| 2.1.14 | 16 / 1 | |
| 2.1.12 | 16 / 1 | |
| 2.1.11 | 16 / 1 | |
| 2.1.10 | 16 / 1 | |
| 2.1.9 | 16 / 1 | |
| 2.1.8 | 16 / 1 | |
| 2.1.7 | 16 / 1 | |
| 2.1.6 | 16 / 1 | |
| 2.1.5 | 16 / 1 | |
| 2.1.4 | 16 / 1 | |
| 2.1.3 | 16 / 1 | |
| 2.1.2 | 16 / 1 | |
| 2.1.1 | 16 / 1 | |
| 2.1.0 | 16 / 1 | |
| 2.0.62 | 16 / 1 | |
| 2.0.61 | 16 / 1 | |
| 2.0.60 | 16 / 1 | |
| 2.0.59 | 16 / 1 | |
| 2.0.58 | 16 / 1 | |
| 2.0.57 | 16 / 1 | |
| 2.0.56 | 16 / 1 | |
| 2.0.55 | 16 / 1 | |
| 2.0.54 | 16 / 1 | |
| 2.0.53 | 16 / 1 | |
| 2.0.52 | 16 / 1 | |
| 2.0.51 | 16 / 1 | |
| 2.0.50 | 16 / 1 | |
| 2.0.49 | 16 / 1 | |
| 2.0.48 | 16 / 1 | |
| 2.0.47 | 16 / 1 | |
| 2.0.46 | 16 / 1 | |
| 2.0.45 | 16 / 1 | |
| 2.0.44 | 16 / 1 | |
| 2.0.43 | 16 / 1 | |
| 2.0.42 | 16 / 1 | |
| 2.0.41 | 16 / 1 |
v2.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.