Analyzed
about 20 hours
ago.
based on code collected
2 days
ago.
Project Summary
Tools for manipulating signed PE-COFF binaries
In a Nutshell, pesign...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a average size development team
with increasing Y-O-Y commits -
...
took an estimated 4 years of effort (COCOMO model)
starting with its first commit in October, 2011
ending with its most recent commit about 1 month ago
Quick Reference
https://github.com/vathpela/pesign
GNU General Public License v2.0 only
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Forbidden
Sub-License
Hold Liable
Required
Distribute Original
Disclose Source
Include Copyright
State Changes
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
-
...
compare projects before you chose one to use
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
by exploring contributors within projects, you can view details on every commit they have made to that project
30 Day SummaryAug 15 2026 — Sep 14 2026
|
12 Month SummarySep 14 2025 — Sep 14 2026
|
