Analyzed
about 16 hours
ago.
based on code collected
about 16 hours
ago.
Project Summary
The aim of the Cryb.to project is to provide a collection of correct, well-written, well-tested and well-documented implementations of both low-level cryptographic primitives and higher-level security-related interfaces under a permissive license.
The Cryb libraries are the first and primary product of the Cryb.to project. They include low-level cryptographic primitives and support code such as safe string handling and containers.
In a Nutshell, Cryb.to...
- ...
- ...
- ...
-
...
took an estimated 14 years of effort (COCOMO model)
starting with its first commit in March, 2014
ending with its most recent commit over 3 years ago
Quick Reference
https://github.com/cryb-to/cryb-to
BSD 3-clause "New" or "Revised" License
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.
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...
-
...
use of OSS increased in 65% of companies in 2016
-
...
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 SummaryJan 19 2026 — Feb 18 2026
|
12 Month SummaryFeb 18 2025 — Feb 18 2026
|
