github not analyzable

Rheosoph/flow-like

github

Flow-Like: Strongly Typed Enterprise Scale Workflows. Built for scalability, speed, seamless AI integration and rich customization.

maintainer
Rheosoph
license
NOASSERTION
first seen
2026-06-01
last seen
2026-06-04
releases · 30d
2
short id
riskinsufficient evidence

Insufficient evidence to grade. This server's source has not been statically analyzed, so a low grade would only mean "nothing found", not "nothing there". We don't show a reassuring grade we can't stand behind. Attested signals (CVEs, provenance) below still apply.

Once the source is analyzed (see the analysis flag in the header), a graded score appears here. How analysis works: methodology.

graded 11m ago · see ecosystem CVEs →

vulnerabilities1 CVEs · grade factor +18
HIGH
Azure invoke presign grants app content write SAS to ExecuteEvents-only users affects ["dev branch through 54d708b9c9b5e3b8182db502edcdff2b454cfad6"]
tool safetyall quiet

No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.

embed badgereadme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/github:Rheosoph/flow-like/badge.svg)](https://mcpobservatory.com/servers/github:Rheosoph/flow-like/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of Rheosoph.