Analyzed
28 days
ago.
based on code collected
29 days
ago.
Project Summary
Wiggle is a program for applying patches that 'patch' cannot apply due to conflicting changes in the original.
Wiggle will always apply all changes in the patch to the original. If it cannot find a way to cleanly apply a patch, it inserts it in the original in a manner similar to 'merge', and report an unresolvable conflict.
In a Nutshell, wiggle for patches...
- ...
- ...
- ...
-
...
took an estimated 4 years of effort (COCOMO model)
starting with its first commit in May, 2006
ending with its most recent commit over 1 year ago
Quick Reference
git://git.neil.brown.name/wiggle
GPL 2
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...
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
data presented on the Open Hub is available through our API
-
...
65% of companies leverage OSS to speed application development in 2016
-
...
anyone with an Open Hub account can update a project's tags
30 Day SummaryDec 30 2024 — Jan 29 2025
|
12 Month SummaryJan 29 2024 — Jan 29 2025
|
