Analyzed
4 months
ago.
based on code collected
4 months
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.
Badges
In a Nutshell, Neos Flow...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a very large development team
with decreasing Y-O-Y commits -
...
took an estimated 673 years of effort (COCOMO model)
starting with its first commit in February, 2008
ending with its most recent commit 4 months 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 )
There are no reported vulnerabilities
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...
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
anyone with an Open Hub account can update a project's tags
-
...
55% of companies leverage OSS for production infrastructure
-
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
30 Day SummaryApr 28 2022 — May 28 2022
|
12 Month SummaryMay 28 2021 — May 28 2022
|
