Analyzed
25 days
ago.
based on code collected
26 days
ago.
Project Summary
Neos Flow (known as FLOW3 in its first releases) is an offspring from the development of the Neos CMS. Flow can be used independently as a development framework.
It's making extensive use of software development paradigms such as Domain-Driven Design, Dependency Injection and AOP.
In a Nutshell, Neos Flow...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a large development team
with decreasing Y-O-Y commits -
...
took an estimated 401 years of effort (COCOMO model)
starting with its first commit in February, 2008
ending with its most recent commit about 1 month ago
MIT License
Permitted
Commercial Use
Modify
Distribute
Sub-License
Private Use
Forbidden
Hold Liable
Required
Include Copyright
Include License
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
Project Vulnerability Report
Security Confidence Index
Poor security track-record
Favorable security track-record
Vulnerability Exposure Index
Many reported vulnerabilities
Few reported vulnerabilities
Did You Know...
-
...
there are over 3,000 projects on the Open Hub with security vulnerabilities reported against them
-
...
anyone with an Open Hub account can update a project's tags
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
data presented on the Open Hub is available through our API
30 Day SummaryMar 11 2025 — Apr 10 2025
|
12 Month SummaryApr 10 2024 — Apr 10 2025
|
