libdeco-ostc

I Use This!

Activity Not Available

Analyzed over 2 years ago. based on code collected over 2 years ago.

Project Summary

The libdeco-ostc project provides library for dive decompression calculation. The library functions perform dive simulation using OSTC dive computer firmware and return decompression schedule information. The used decompression model is Buhlmann (ZH-L16C) with Gradient Factors.

C API (libdeco library) and Python API (DecoMecha module) are supported.

The OSTC dive computer and its firmware is produced by HeinrichsWeikamp company:

http://www.heinrichsweikamp.com/
https://bitbucket.org/heinrichsweikamp/ostc2_code

The code of the library is licensed under GPLv3 license (the same as OSTC firmware), see COPYING file for details. As stated in the license, there is no warranty, so any diving while using data provided by the library is on
diver's own risk.

In a Nutshell, libdeco-ostc...

...
has had 988 commits made by 8 contributors
representing 1,378 lines of code
...
is mostly written in Python
with a very well-commented source code
...
has a codebase with a long source history
maintained by nobody
with stable Y-O-Y commits
...
took an estimated 1 years of effort (COCOMO model)
starting with its first commit in January, 2010
ending with its most recent commit over 8 years ago

Quick Reference

Project Links:

Add some Project Link(s)

Code Locations:

https://bitbucket.org/wrobell/li...

Similar Projects:

Managers:

wrobell

Licenses

GNU General Public License v3.0 only

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...

...
in 2016, 47% of companies did not have formal process in place to track OS code
...
by exploring contributors within projects, you can view details on every commit they have made to that project
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog

About Project Security