CrissCross

I Use This!

Inactive

Analyzed about 9 hours ago. based on code collected about 9 hours ago.

Project Summary

CrissCross is a small open source cross platform C++ library for console and file I/O, CPU identification (CPUID), hashing (MD2, MD4, MD5, SHA-1, SHA-256, SHA-512, Tiger), sockets (TCP and UDP only currently), and data structures (LList, DArray, RedBlackTree, AVLTree, SplayTree, etc).

CrissCross is designed to run on Windows, Linux, FreeBSD, OpenBSD, NetBSD, Mac OS X, and even the Nintendo DS. Other platforms may become supported upon request.

The main idea behind CrissCross is the ability to write a program using identical calls on the major platforms, without needing to rewrite code.

In a Nutshell, CrissCross...

...
has had 615 commits made by 6 contributors
representing 12,292 lines of code
...
is mostly written in C++
with an average number of source code comments
...
has a well established, mature codebase
maintained by nobody
with stable Y-O-Y commits
...
took an estimated 3 years of effort (COCOMO model)
starting with its first commit in October, 2008
ending with its most recent commit almost 4 years ago

Quick Reference

Project Links:

Homepage
Documentation
Download
Forums

Code Locations:

https://github.com/tycho/crisscross

Similar Projects:

Managers:

Steven Noonan

Licenses

BSD 4-clause (University of California-Specific)

Permitted

Commercial Use

Modify

Distribute

Place Warranty

Forbidden

Hold Liable

Use Trademarks

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.

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
...
you can embed statistics from Open Hub on your site
...
in 2016, 47% of companies did not have formal process in place to track OS code
...
compare projects before you chose one to use