RepoPilot

flowable/flowable-engine · Security & risks

Authoritative risk signals for flowable/flowable-engine — dependency CVEs (deps.dev), OpenSSF Scorecard, and GitHub Code Scanning. Not a substitute for your own security review.

ArchitectureSecurity & risksDependenciesLicenseMaintenanceAlternativesVsFull analysis

Dependency CVEs (deps.dev)

0
Critical
0 direct
0
High
0 direct
0
Moderate
0
Deps scanned
0 direct

OpenSSF Scorecard · 4.3/10

  • Branch-Protection—
  • CII-Best-Practices0/10
  • Token-Permissions0/10
  • Security-Policy0/10
  • Signed-Releases0/10
  • Binary-Artifacts0/10
  • Fuzzing0/10
  • SAST0/10

GitHub Code Scanning · 0 open / 0 total

Tools: —

Ask AI about flowable/flowable-engine

Grounded in the actual source code. Pick a starter question or write your own.

What does this repo do, in one paragraph?How would I get started using it?What are the main alternatives?Show me the entry point.
Or write your own question

Informational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.