Liquid War 6

I Use This!

Inactive

Analyzed 1 day ago. based on code collected 1 day ago.

Project Summary

Liquid War 6 is a unique multiplayer wargame. Your army is a blob of liquid and you have to try and eat your opponents. Rules are very simple yet original, they have been invented by Thomas Colcombet. It is possible to play alone against the computer but the game is really designed to be played with friends, on a single computer, on a LAN, or on Internet.

In a Nutshell, Liquid War 6...

...
has had 1,642 commits made by 6 contributors
representing 181,370 lines of code
...
is mostly written in C
with a well-commented source code
...
has a well established, mature codebase
maintained by nobody
with stable Y-O-Y commits
...
took an estimated 47 years of effort (COCOMO model)
starting with its first commit in March, 2010
ending with its most recent commit about 10 years ago

Quick Reference

Project Links:

Homepage
Download

Code Locations:

git://git.sv.gnu.org/liquidwar6.git

Similar Projects:

Managers:

ufoot

Licenses

GNU General Public License v3.0 or later

Permitted

Commercial Use

Modify

Distribute

Place Warranty

Use Patent Claims

Forbidden

Sub-License

Hold Liable

Required

Distribute Original

Disclose Source

Include Copyright

State Changes

Include License

Include Install Instructions

These details are provided for information only. No information here is legal advice and should not be used as such.

All Licenses

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

About Project Vulnerability Report

Did You Know...

...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
...
data presented on the Open Hub is available through our API
...
in 2016, 47% of companies did not have formal process in place to track OS code
...
compare projects before you chose one to use