BEEN Benchmarking Environment

I Use This!

Activity Not Available

Analyzed about 3 years ago. based on code collected over 3 years ago.

Project Summary

BEEN is a generic tool for automated benchmarking in a heterogeneous distributed environment. BEEN automates all steps of a benchmark experiment from software building and deployment through measurement and load monitoring to evaluation of results. The notable features include separation of the measurement from the evaluation and an ability to adaptively scale the benchmark experiment based on the evaluation.

In a Nutshell, BEEN Benchmarking Environment...

...
has had 594 commits made by 9 contributors
representing 1,161,160 lines of code
...
is mostly written in XSL Transformation
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 320 years of effort (COCOMO model)
starting with its first commit in December, 2006
ending with its most recent commit over 10 years ago

Quick Reference

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

...
there are over 3,000 projects on the Open Hub with security vulnerabilities reported against them
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
...
learn about Open Hub updates and features on the Open Hub blog

About Project Security

Code locations have been removed since last analysis

At one point, Open Hub analyzed source code for this project based on code location(s) available at that time. Since then, the code locations have been removed.