Analyzed
about 10 hours
ago.
based on code collected
about 10 hours
ago.
Project Summary
The purpose of the ESAPI is to provide a simple interface that provides all the security functions a developer is likely to need in a clear, consistent, and easy to use way. The ESAPI architecture is very simple, just a collection of classes that encapsulate the key security operations most applications need.
In a Nutshell, owasp-esapi-js...
- ...
- ...
- ...
-
...
took an estimated 2 years of effort (COCOMO model)
starting with its first commit in November, 2009
ending with its most recent commit over 1 year ago
Quick Reference
Organization:
https://github.com/ESAPI/owasp-e...
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...
-
...
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
-
...
anyone with an Open Hub account can update a project's tags
30 Day SummaryOct 31 2022 — Nov 30 2022
|
12 Month SummaryNov 30 2021 — Nov 30 2022
|
